User's Guide

Compiler Options for the 64-bit Environment

The compiler options that are described in this section enable you to do the following:

• Develop applications for the 64-bit environment
• Help migrate source code from the 32-bit environment to a 64-bit environment
• Determine whether the old 64-bit ABI or the new 64-bit LDT ABI is generated

Some of these options already exist in the 32-bit environment but have new settings particular to the 64-bit architecture. This section only covers the new settings for these cases. The options that are grouped here are primarily for developers who are targetting 64-bit platforms.

-q32 Option

Syntax:

-q32

Enables 32-bit compilation bit mode (or, more briefly, 32-bit mode) support in a 64-bit environment. The -q32 option indicates the compilation bit mode and, together with the -qarch option, determines the target machines that the 32-bit executable will run on.

Rules:

• The default integer and default real size are 4 bytes in 32-bit mode.
• The default integer pointer size is 4 bytes in 32-bit mode.
• 32-bit object modules are created in 32-bit mode.
• -q32 is the default if you have not specified either -q32 or -q64 and if you have not set the OBJECT_MODE environment variable. For a description of the OBJECT_MODE environment variable, see Default Bit Mode.
• -q64 may override -q32.
• All settings for -qarch are compatible with -q32. If you specify -q32, the default -qarch suboption is com, and the default -qtune suboption for -q32 is pwr2.
• The LOC intrinsic returns an INTEGER(4) value.

Examples

• Using 32-bit compilation mode and targetting the 601 architecture:

     -qarch=ppc -q32
  

• Now keep the same compilation mode, but change the target to RS64I:

     -qarch=ppc -q32 -qarch=rs64a
  

  Notice that the last setting for -qarch wins.

• Now keep the same target, but change the compilation mode to 64-bit:

     -qarch=ppc -q32 -qarch=rs64a -q64
  

  Notice that specifying -q64 overrides the earlier instance of -q32.

-q64 Option

Syntax:

-q64={laregetype|nolargetype}
 

Indicates the 64-bit compilation bit mode and, together with the -qarch option, determines the target machines on which the 64-bit executable will run. The -q64 option indicates that the object module will be created in 64-bit object format and that the 64-bit instruction set will be generated. Note that you may compile in a 32-bit environment to create 64-bit objects, but you must link them in a 64-bit environment with the -q64 option.

Defaults

-q64=largetype is the default setting when compiling with -q64 on AIX 5.1 and above. Use the -q64=largetype suboption to generate the 64-bit LDT ABI. However, -q64=nolargetype can be specified to generate the old 64-bit non-LTD ABI on AIX 5.1 and above.

-q64=nolargetype is the default setting when compiling with -q64 on AIX 4.3.3. Specify the -q64=nolargetype suboption to generate the old 64-bit non-LDT ABI. Specify -q64=largetype to generate 64-bit LDT ABI objects on older versions of AIX that do not support Large Data Types.

Rules:

• Settings for -qarch that are compatible with -q64 are as follows:
  • -qarch=auto (if compiling on a 64-bit system)
  • -qarch=com
  • -qarch=ppc
  • -qarch=rs64a
  • -qarch=rs64b
  • -qarch=rs64c
  • -qarch=pwr3
  • -qarch=pwr4
• The default -qarch setting for -q64 is ppc.
• 64-bit object modules are created in 64-bit mode.
• -q32 may override -q64.
• -q64 will override a conflicting setting for -qarch. For example,

  -q64 -qarch=601
  

  will result in the setting -q64 -qarch=ppc along with a warning message.
• The default tune setting for -q64 is -qtune=pwr3.
• The default integer and default real size is 4 bytes in 64-bit mode.
• The default integer pointer size is 8 bytes in 64-bit mode.
• The maximum array size increases to approximately 2**40 bytes (in static storage) or 2**60 bytes (in dynamic allocation on the heap). The maximum dimension bound range is extended to -2**63, 2**63-1 bytes. The maximum array size for array constants has not been extended and will remain the same as the maximum in 32-bit mode. The maximum array size that you can initialize is 2**28 bytes.
• The maximum iteration count for array constructor implied DO loops increases to 2**63-1 bytes.
• The maximum character variable length extends to approximately 2**40 bytes. The maximum length of character constants and subobjects of constants remains the same as in 32-bit mode, which is 32 767 bytes (32 KB).
• The LOC intrinsic returns an INTEGER(8) value.
• When you use -qautodbl=dblpad in 64-bit mode, you should use -qintsize=8 to promote INTEGER(4) to INTEGER(8) for 8 byte integer arithmetic.
• When multiple -q64 options are used on one command line, the following rules of precedence apply:
  • The -q64=largetype and -q64=nolargetype suboptions override all previous -q64 options.
  • -q64 without an explicit suboption is ignored if -q64=largetype or -q64=nolargetype has been specified previously. Otherwise, -q64 implies:
    • The largetype suboption on AIX 5.1 and above.
    • The nolargetype suboption on AIX 4.3.3.

Restrictions:

• Objects that are generated with the 64-bit LDT ABI are not compatible with 64-bit non-LDT ABI objects. 64-bit LDT ABI objects cannot be linked with 64-bit non-LDT ABI objects on any level of AIX.
• 64-bit LDT ABI objects must be linked on AIX 5.1 and above. Objects created with the old 64-bit non-LDT ABI must be linked on AIX 4.3.3.
• 64-bit LDT ABI applications cannot be loaded or executed on AIX 4.3.3. 64-bit non-LDT ABI applications cannot be loaded or executed on AIX 5.1 and above. Existing 64-bit applications must be recompiled to run on AIX 5.1 and above!
• Module (.mod) files created with the -q64=largetype suboption cannot be used for non-LDT compilation. Similarly, non-LDT module files cannot be used for 64-bit LDT compilation.
• New xlfutility and f_pthread 64-bit LDT module files are provided in a new directory called:

  /usr/lpp/xlf/include_64ldt.
   
   
  

• If the include_64 attribute is used in the xlf.cfg file to specify an alternate directory for 64-bit include and module files, the compiler will append 'ldt' to the specified directory name at compilation time with -q64=largetype. For example, if the xlf.cfg file specifies:

  include_64=/home/joe/inc64dir
  

  and the compiler is invoked with the -q64 option on an AIX 5L system, the compiler will actually search:

  /home/joe/inc64dirldt.
   
   
  

• Each of the following situations will produce an error message:
  1. Attempting to link, load or execute conflicting 64-bit ABI objects on any level of AIX
  2. Attempting to link, load or execute 64-bit LDT ABI objects on AIX 4.3.3
  3. Attempting to link, load or execute 64-bit non-LDT ABI objects on AIX 5.1 and above.

Examples

In this example 64-bit compilation that targets the RS64I (also known as RS64a):

-q32 -qarch=rs64a -q64

In this example 64-bit compilation that targets the common group of 64-bit architectures (which currently consists only of the RS64I, RS64II, RS64III, POWER3, and POWER4):

-q64 -qarch=com

In this example, the -qarch option conflicts with -q64:

-qarch=601 -q64

which results in a suboption setting of -q64 -qarch=ppc and a warning message.

In the example that follows, the -qarch option conflicts with -q64:

-q64 -qarch=601

which results in a suboption setting of -q64 -qarch=ppc and a warning message.

The following valid example assumes that compilation is on AIX 5L:

xlf90 a.f b.f -q64=largetype -o ldt_app

is equivalent to:

xlf90 a.f b.f -q64 -o ldt_app

because -q64=largetype is the default when compiling on a version of AIX with LDT support.

As this example shows, source files can be compiled on AIX 4.3.3:

xlf90 a.f b.f -q64=largetype -c

However, the resulting object files, a.o and b.o,must now be linked on AIX 5L.

In the following invalid example, an attempt is made to link new 64-bit ABI objects and old 64-bit ABI objects. This will produce an error on any level of AIX:

xlf90 a.f -q64=largetype -c
xlf90 b.f -q64=nolargetype -c
xlf90 a.o b.o -q64 -o ldt_app

-qarch=rs64a Option

Syntax:

-qarch=rs64a

Indicates that the target architecture for the executable to run on is the RS64I.

Rules:

• You can specify the -qarch=rs64a option with either the -q32 or -q64 option.
• The RS64I belongs to the 64-bit common architecture group that is specified with the combination of options -qarch=com -q64.
• The supported tune option for -qarch=rs64a is -qtune=rs64a. The default tune option for -qarch=rs64a is -qtune=rs64a.

Related Information:

For more information on the -qarch compiler option, see -qarch Option.

-qarch=rs64b Option

Syntax:

-qarch=rs64b

Indicates that the target architecture for the executable to run on is the RS64II.

Rules:

• You can specify the -qarch=rs64b option with either the -q32 or -q64 option.
• The RS64II belongs to the 64-bit common architecture group that is specified with the combination of options -qarch=com -q64.
• The supported tune option for -qarch=rs64b is -qtune=rs64b. The default tune option for -qarch=rs64b is -qtune=rs64b.

Related Information:

For more information on the -qarch compiler option, see -qarch Option.

-qarch=rs64c Option

Syntax:

-qarch=rs64c

Indicates that the target architecture for the executable to run on is the RS64III.

Rules:

• You can specify the -qarch=rs64c option with either the -q32 or -q64 option.
• The RS64III belongs to the 64-bit common architecture group that is specified with the combination of options -qarch=com -q64.
• The supported tune option for -qarch=rs64c is -qtune=rs64c. The default tune option for -qarch=rs64c is -qtune=rs64c.

Related Information:

For more information on the -qarch compiler option, see -qarch Option.

-qtune=rs64a Option

Syntax:

-qtune=rs64a

Tune optimizations for the PowerPC RS64I processor.

You can specify the -qtune=rs64a option when you also specify any of the following options:

• -qarch=rs64a
• -qarch=ppc
• -qarch=com
• -qarch=auto (if compiling on an RS64I system)

The -qtune=rs64a option is the default for the -qarch=rs64a option.

Related Information:

For more information on the -qtune compiler option, see -qtune Option.

-qtune=rs64b Option

Syntax:

-qtune=rs64b

Tune optimizations for the PowerPC RS64II processor.

You can specify the -qtune=rs64b option when you also specify any of the following options:

• -qarch=rs64b
• -qarch=ppc
• -qarch=com
• -qarch=auto (if compiling on an RS64II system)

The -qtune=rs64b option is the default for the -qarch=rs64b option.

Related Information:

For more information on the -qtune compiler option, see -qtune Option.

-qtune=rs64c Option

Syntax:

-qtune=rs64c

Tune optimizations for the PowerPC RS64III processor.

You can specify the -qtune=rs64c option when you also specify any of the following options:

• -qarch=rs64c
• -qarch=ppc
• -qarch=com
• -qarch=auto (if compiling on an RS64III system)

The -qtune=rs64c option is the default for the -qarch=rs64c option.

Related Information:

For more information on the -qtune compiler option, see -qtune Option.

-qwarn64 Option

Syntax:

-qwarn64 | -qnowarn64

Aids in porting code from a 32-bit environment to a 64-bit environment by detecting the truncation of an 8-byte integer pointer to 4 bytes. The -qwarn64 option uses informational messages to identify statements that may cause problems with the 32-bit to 64-bit migration. The option name provides compatibility with the C for AIX compiler.

Rules:

• The default setting is -qnowarn64.
• You can use the -qwarn64 option in both 32-bit and 64-bit modes.
• The compiler flags the following situations with informational messages:
  • The assignment of a reference to the LOC intrinsic to an INTEGER(4) variable.
  • The assignment between an INTEGER(4) variable or INTEGER(4) constant and an integer pointer.
  • The specification of an integer pointer within a common block. We recommend the -qextchk option for common block length changes.
  • The specification of an integer pointer within an equivalence statement.
• We recommend the -qextchk option and interface blocks for argument checking.