C++ Compiler

From RAD Studio
Jump to: navigation, search

Go Up to Building


Project > Options > Building > C++ Compiler

Use this dialog box to set C++ Compiler options.

Options Description

Target, Apply, Save

See Target Options.

Common items

See Common Items on Project Options Pages.

C++ Compilation Options

Classic Compiler

Classic Compiler options Description Compiler switches
bcc32 bcc32c bcc64 bccx64

Use 'classic' Borland compiler

Enables either the classic BCC32 compiler or the clang-enhanced BCC32C compiler as the C++ compiler for 32-bit Windows platforms.

Use this option to switch a project from BCC32 to BCC32C and vice versa. You can set this option to:

  • True: BCC32 is enabled as the C++ compiler for projects that target 32-bit Windows platforms.
  • False: BCC32C is enabled as the C++ compiler for projects that target 32-bit Windows platforms.

Default = True

Platform not supported

Platform not supported

General Compilation Options

General Compilation options Description Compiler switches
bcc32 bcc32c bcc64 bccx64

Calling convention

Pascal
(-p)
Tells the compiler to generate a Pascal calling sequence for function calls (do not generate underbars, all uppercase, calling function cleans stack, pushes parameters left to right). This is the same as declaring all subroutines and functions with the __pascal keyword. The resulting function calls are usually smaller and faster than those made with the C (-pc) calling convention. Functions must pass the correct number and type of arguments. You can use the __cdecl, __fastcall, or __stdcall keyword to specifically declare a function or subroutine using another calling convention.

-p

Platform not supported

Platform not supported

Platform not supported
C

(-pc)*
Tells the compiler to generate a C calling sequence for function calls (generate underbars, case sensitive, push parameters right to left). This is the same as declaring all subroutines and functions with the __cdecl keyword. Functions declared using the C calling convention can take a variable parameter list (the number of parameters does not need to be fixed).
You can use the __pascal, __fastcall, or __stdcall keyword to specifically declare a function or subroutine using another calling convention. This is the default.

-pc -mcdecl -mcdecl -mcdecl
_msfastcall

(-pm)
Tells the compiler to substitute the __msfastcall calling convention for any function without an explicitly declared calling convention.

-pm Platform not supported Platform not supported Platform not supported
Fastcall (register)

(-pr)
Forces the compiler to generate all subroutines and all functions using the Register parameter-passing convention, which is equivalent to declaring all subroutines and functions with the __fastcall keyword. With this option enabled, functions or routines expect parameters to be passed in registers.

You can use the __pascal, __cdecl, or __stdcall keyword to specifically declare a function or subroutine using another calling convention.

-pr -mfastcall -mfastcall -mfastcall
stdcall

(-ps)
Tells the compiler to generate a stdcall calling sequence for function calls (does not generate underscores, preserve case, called function pops the stack and pushes parameters right to left). This is the same as declaring all subroutines and functions with the __stdcall keyword. Functions must pass the correct number and type of arguments.

You can use the __cdecl, __pascal, __fastcall keyword to specifically declare a function or subroutine using another calling convention.

Default = C (-pc)

-ps -mrtd, -mstdcall -mrtd, -mstdcall -mrtd, -mstdcall

Data Alignment

Byte
(-a1)
Does not force the alignment of variables or data fields to any specific memory boundaries. The compiler aligns data at even or odd addresses, depending on the next available address. While byte alignment produces more compact programs, the programs tend to run slower. The other data alignment options increase the speed at which 80x86 processors fetch and store data.

-a1

-fpack-struct=1

N/A N/A
Word

(-a2)
2 byte data alignment. Aligns non-character data at even addresses. Automatic and global variables are aligned properly. char and unsigned char variables and fields can be placed at any address; all others are placed at even-numbered addresses.

-a2 -fpack-struct=2 N/A N/A
Double word

(-a4)
4 byte data alignment. Aligns non-character data at 32-bit word (4-byte) boundaries. Data type sizes of less than 4 bytes are aligned on their type size.

-a4 -fpack-struct=4 N/A N/A
Quad word

(-a8)*
8 byte data alignment. Aligns non-character data at 64-bit word (8-byte) boundaries. Data with type sizes of less than 8 bytes are aligned on their type size. This is the default.

-a8 -fpack-struct=8 N/A N/A
Paragraph

(-a16)
16 byte data alignment. Aligns non-character data at 128-bit (16-byte) boundaries. Data with type sizes of less than 16 bytes are aligned on their type size.

Default = Quad word (8)

-a16 -fpack-struct=16 N/A N/A

Disable C++ access control

Tells the compiler not to enforce access control. That is, the compiler does not emit an error if a protected or private member is accessed when it should not be accessible. Use this option if you had code that BCC32 allowed, but BCC64 treats as violating access control (or better, update your code to match the rule used by BCC64).

Default = False

Platform not supported

N/A

-fno-access-control

-fno-access-control

Enable batch compilation

Enables batch compilation.

When this option is enabled, all the source modules are passed to the C++ compiler on the same command line, instead calling the compiler once for each source module. For batch compiles, build events are generated for the entire batch compile, not for single files. Similarly, a batch compile uses one set of project options, with no per-file overrides allowed.

If you are using a Clang-enhanced C++ compiler, you can use "Enable batch compilation" in combination with "Run C++ compiler in a separate process" to enable parallel compilation. Clang-enhanced compilers for 32-bit platforms stop the batch compilation after a file fails to compile.

Default = off

Maximum errors

(-j)

Causes batch compilation to stop after the specified number of errors has been detected. You can enter any number from 0 through 255.

Default = 1

Entering 0 causes compilation to continue until the end of the file or this warning limit has been reached, whichever comes first.

-j -ferror-limit N/A N/A
Maximum warnings

(-g)

Causes batch compilation to stop after the specified number of warnings has been detected. You can enter any number from 0 through 255.

Default = 255

Entering 0 causes compilation to continue until either the end of the file or this error limit has been reached, whichever comes first.

-g Platform not supported Platform not supported Platform not supported
Stop on first error
(-jb)

Stops batch compilation after the first file that causes errors. For example:

BCC32.exe -c -gb *.ccp
BCC32.exe -c -gb file1.cpp file2.cpp

Without the -jb flag, batch compilations can continue to the next scheduled file, even after an earlier file has caused an error.

-jb Platform not supported Platform not supported Platform not supported

Extended error info

The compiler generates more extended information on errors.

Default = False

-Q

Platform not supported

Platform not supported

Platform not supported

Force C++ compile

Causes the compiler to compile all source files as C++ files, regardless of their extension.

Default = False

-P

-x c++

-x c++

-x c++

Instruction set

80386
(-3)*
Generates 80386 protected-mode compatible instructions. This is the default.

-3

Platform not supported

Platform not supported

Platform not supported
80486

(-4)
Generates i486 protected-mode compatible instructions.

-4 Platform not supported Platform not supported Platform not supported
Pentium

(-5)
Generates Pentium instructions. While this option increases the speed at which the application runs on Pentium machines, expect the program to be a bit larger than when compiled with the 80386 or i486 option. Also, Pentium-compiled code sustains a performance hit on non-Pentium systems.

-5 Platform not supported Platform not supported Platform not supported
Pentium Pro

(-6)
Generates Pentium Pro instructions.

Default = 80386

-6 Platform not supported Platform not supported Platform not supported

Integer-sized enums

Allocates a whole word (a four-byte int for 32-bit programs) for enumeration types (variables of type enum).

When this option is off (-bi-), the compiler allocates the smallest integer that can hold the enumeration values: the compiler allocates an unsigned or signed char if the values of the enumeration are within the range of 0 through 255 (minimum) or -128 through 127 (maximum), or an unsigned or signed short if the values of the enumeration are within the following ranges: 0..65535 or -32768..32767.

The compiler allocates a four-byte int (32-bit) to represent the enumeration values if any value is out of these ranges.

Default = True

-bi

-fshort-enums

N/A

N/A

Integer-typed enums

Enables Integer-sized enums (-bi, described above) and treats enums as ints from a typechecking point of view (relaxes typechecking for enums).
When this option is off (-b-), the compiler makes sizeof(enum x) as small as possible and applies enum rules for type checking.

Default = False

-b

-fshort-enums

N/A

N/A

Language compliance

ANSI
(-A)

Use ANSI keywords and extensions. Compiles C and C++ ANSI-compatible code, allowing for maximum portability. Non-ANSI keywords are ignored as keywords.

-A

-fno-borland-extensions

N/A N/A
GNU
(-AG)Use keywords and extensions of Gcc, the GNU compiler collection, which is distributed by the Free Software Foundation at http://gcc.gnu.org/. Tells the compiler to recognize specific GNU keywords and extensions, such as __attribute__, __const, __inline__, __signed__. See GNU Attributes.
-AG Platform not supported Platform not supported Platform not supported
K & R

(-AK) Use Kernighan and Ritchie (KR) keywords and extensions. Tells the compiler to recognize only the KR extension keywords and treat any C++ extension keywords as normal identifiers.

-AK Platform not supported N/A N/A
Borland/CodeGear

(also -A-) (-AT)* Use Borland/CodeGear/Embarcadero C++ keywords and extensions. Tells the compiler to recognize extensions to the C language keywords, including near, far, huge, asm, cdecl, pascal, interrupt, _export, _ds, _cs, _ss, _es, and the register pseudovariables ( _AX, _BX, and so on). This is the default.

-AT -fborland-extensions Platform not supported Platform not supported
Unix System V

(-AU) Use UNIX System V keywords and extensions. Tells the compiler to recognize only UNIX V keywords and treat any of the Borland/CodeGear/Embarcadero C++ extension keywords as normal identifiers.

Hint: If you get declaration syntax errors from your source code, check that this option is set to Borland/CodeGear.

Default = Borland/CodeGear.

-AU Platform not supported N/A N/A

Register variables

None
(-r-)*
Disables the use of register variables. Tells the compiler not to use register variables, even if you have used the register keyword. This is the default.

-r- Platform not supported Platform not supported Platform not supported
Explicit

(-rd)
Use register variables only if you use the register keyword and a register is available. Use this option or the Always option (-r) to optimize the use of registers. You can use -rd in #pragma options.

-rd Platform not supported Platform not supported Platform not supported
Always

(-r)
Automatically assign register variables if possible, even when you do not specify a register variable by using the register keyword. Generally, you can use Always, unless you are interfacing with preexisting assembly code that does not support register variables.

Default = None

-r Platform not supported Platform not supported Platform not supported

Set the maximum number of errors to emit before stopping (0 = no limit)

To specify the number of errors to allow for the 64-bit C++ compiler, select the number in this field and type the number you want to set. Default = 1

Platform not supported

N/A

-ferror-limit

-ferror-limit

Short enums

Tells the 64-bit compiler to use minimally sized enums.

Allocate to an enum type only as many bytes as it needs for the declared range of possible values.

Default = False

Interger-sized enums option

Interger-sized enums option

-fshort-enums

-fshort-enums

Standard stack frames

Generates a standard stack frame (standard function entry and exit code). This is helpful when debugging since it simplifies the process of stepping through the stack of called subroutines.

When this option is off, any function that does not use local variables and has no parameters is compiled with abbreviated entry and return code. This makes the code smaller and faster.

The Standard Stack Frame option should always be on when you compile a source file for debugging.

Default = True

-k

Platform not supported

Platform not supported

Platform not supported

Child Pages

See Also