Compilers: IBM Advance Toolchain 5.0

Compilers: IBM Advance Toolchain 6.0

Operating systems: SUSE Linux Enterprise 10, SUSE Linux Enterprise 11, and Red Hat Enterprise Linux Advanced Platform 5 and 6

Last updated: May 2013

]]>A sample list of supported values for this flag are

- power
- power2
- power3
- power4
- power5
- power5+
- power6
- power7

`-fno-align-functions` and `-falign-functions=1` are
equivalent and mean that functions will not be aligned.

Some assemblers only support this flag when *n* is a power of two; in
that case, it is rounded up.

If *n* is not specified, use a machine-dependent default.

If *n* is not specified, use a machine-dependent default.

If *n* is not specified, use a machine-dependent default.

Well, I know that **you**, as the well informed and well-
connected (with your compiler vendor) will be able to document ALL of
your implicitly included flags.

Pay special attention to code like this:

union a_union { int i; double d; }; int f() { a_union t; t.d = 3.0; return t.i; }

The practice of reading from a different union member than the one
most recently written to (called ``type-punning'') is common. Even
with `-fstrict-aliasing`, type-punning is allowed, provided the
memory is accessed through the union type. So, the code above will
work as expected. However, this code might not:

int f() { a_union t; int* ip; t.d = 3.0; ip = &t.i; return *ip; }]]>

- -fno-math-errno
- -funsafe-math-optimizations
- -fno-trapping-math
- -ffinite-math-only
- -fno-signaling-nans

Use of this option can result in incorrect output for programs which depend on an exact implementation of IEEE or ISO rules/specifications for math functions.

]]>Use of this option may result in incorrect output for programs which depend on an exact implementation of IEEE or ISO rules/specifications for math functions.

]]>Use of this option may result in incorrect output for programs which depend on an exact implementation of IEEE or ISO rules/specifications for math functions.

]]>Use of this option may result in incorrect output for programs which depend on an exact implementation of IEEE or ISO rules/specifications for math functions.

]]>If all calls to a given function are integrated, and the function is declared "static", then the function is normally not output as assembler code in its own right.

]]>If all calls to a given function are integrated, and the function is declared "static", then the function is normally not output as assembler code in its own right.

]]>