fegettrapenable(3M)fegettrapenable(3M)NAME
fegettrapenable() - get floating-point exception trap enables
SYNOPSIS DESCRIPTION
The function determines which floating-point exception traps are currently enabled.
USAGE
To use this function, compile either with the default option or with the and options. Make sure your program includes
For HP Integrity servers, specify on the compiler command line or place the call to this function under the effect of an affirmative
pragma:
If the pragma is placed outside of any top-level declarations in a file, the pragma will apply to all declarations in the compilation fol-
lowing the pragma until another pragma is encountered or until the end of the file is reached.
If the pragma is placed at the beginning of a block (compound statement), the pragma will apply until another pragma is encountered or
until the end of the block is reached.
For PA-RISC, you might need to use the compiler option in order to prevent optimizations that can undermine the specified behavior of this
function.
Link in the math library by specifying on the compiler or linker command line.
For more information, see the at the following site:
RETURN VALUE
The function returns the bitwise OR of the floating-point exception macros corresponding to the currently enabled exception traps. The
macros are and represents all the floating-point exceptions.
ERRORS
No errors are defined.
EXAMPLES
Retrieve the current trap settings and determine whether a trap for the divide by zero exception is enabled.
AUTHOR
was developed by HP and is not required by any current standard.
SEE ALSO feclearexcept(3M), fegetexceptflag(3M), feraiseexcept(3M), fesetexceptflag(3M), fesettrapenable(3M), fenv(5).
fegettrapenable(3M)
Check Out this Related Man Page
feclearexcept(3M)feclearexcept(3M)NAME
feclearexcept() - clear floating-point exception flags
SYNOPSIS
HP Integrity Server Only
PA-RISC Only
DESCRIPTION
The function clears the exception flags represented by its argument. The argument can be constructed as a bitwise OR of the exception
macros: and represents all the floating-point exceptions.
USAGE
To use this function, compile either with the default option or with the and options. Make sure your program includes
For Integrity servers, specify on the compiler command line or place the call to this function under the effect of an affirmative pragma:
If the pragma is placed outside of any top-level declarations in a file, the pragma will apply to all declarations in the compilation fol-
lowing the pragma until another pragma is encountered or until the end of the file is reached.
If the pragma is placed at the beginning of a block (compound statement), the pragma will apply until another pragma is encountered or
until the end of the block is reached.
For PA-RISC, you might need to use the +Onomoveflops compiler option in order to prevent optimizations that can undermine the specified
behavior of this function.
Link in the math library by specifying on the compiler or linker command line.
For more information, see the
RETURN VALUE
Integrity Server Only
This function always returns 0, indicating all specified exceptions were cleared.
PA-RISC Only
None.
ERRORS
No errors are defined.
EXAMPLES
Clear the underflow and inexact floating-point exception flags:
Clear all floating-point exception flags:
SEE ALSO fegetexceptflag(3M), fegettrapenable(3M), feraiseexcept(3M), fesetexceptflag(3M), fesettrapenable(3M), fetestexcept(3M), fenv(5).
STANDARDS CONFORMANCE
: ISO/IEC C99 (including Annex F, "IEC 60559 floating-point arithmetic")
feclearexcept(3M)
hello.
i use follow sentences in include files in SCO unix is ok.
#pragma pack(1)
struct dddd {
int iD1;
char cCh1;
...
};
#pragma pack()
but in hp-9000 unix , not ok when compiling, cc not support
#pragma pack(1)
how to settle the question ?
... (1 Reply)
hi...
just wanted to check how i can the entry point of a program...
i tried using the #pragma directive but it doesnt seem to be workin...
#pragma comment(linker,"/ENTRY:startupfunction")
#include<stdio.h>
void startupfunction()
{
printf("in print\n");
main();
}
int main()
{... (4 Replies)
Hi, guys,
today, I have copied a simple script which runs correctly on a computer to another one. But, the latter informs me:
Floating point exception!
@ ./command_module a b c
where command_module is the module compiled by myself.
So, I have fixed it by following steps:
1.... (5 Replies)
Hi,
I have a question regarding pragma page. What is the advantage of using this pragma? Also the description tells that it is a compiler directive to start of in a new page. Does the page here refer to the page in memory where the set of code under the pragma page will be starting in a new... (3 Replies)
I know it looks like a stupid question, but i really wanna know the reason.
Actually, i think it's because the c compiler will detect it as the end of file "EOF" of the program, but, am i wrong? because it compiles it anyway, but keep showing warnings like "no new line at the end of file".
I... (8 Replies)
I am not able to find warn-codes that should be used in
#pragma warn -<code>
directive!:wall:
Could anybody advise where I can see a list of warnings with codes that (as I understand) should be 3-letters code?
I have a pro-C program that produces some warnings.
(Do not advise,... (4 Replies)
Quick question for the community of GCC programmers.
I have code that uses:
#pragma align 4
(as an example).
Now this code has compiled for many years on a few different platforms and GCC versions.
Recently I got warning messages about it (using gcc 4.9.2 on Solaris) and I wondered... (0 Replies)
I saw a header (.h) file with mixture of "regular" function declarations and other extern function declarations. As I was told all function declarations are implicitly external and the extern on functions declarations is superfluous. Here my focus is on function declaration, not variable yet.
int... (2 Replies)