cc/CC

compile command (UNIX)

Syntax:

Invoke the C compiler:

cc [options] [operands]
c89 [options] [operands]

Invoke the C++ compiler:

CC [options] [operands]

Options:

-0

Produce 16-bit object code, using only 8086 instructions. The code runs on the 16- or 32-bit version of QNX.

-2

Produce 16-bit object code, using 286 instructions. The code runs on the 16- or 32-bit version of QNX if QNX is operating on a processor upwardly compatible with the Intel 286.

-3

Produce 32-bit object code, using 386 instructions optimized for Intel 386 instruction timings. The code runs only on the 32-bit version of QNX.

-3r

32-bit, using register calling conventions.

-3s

32-bit, using stack calling conventions.

-4

Same as -3, but for 486 instruction timings. This is the default. For maximum performance, you should also use the r optimization (see the -O option).

-5

Same as -3, but for Pentium instruction timings. For maximum performance, you should also use the r optimization (see the -O option).

-A library

Combine all object files provided as operands and build this new library. The library filename is given the .lib suffix.

-a library

Combine all object files provided as operands and add them to this existing library. The library filename is assumed to have a .lib suffix.

-B

Search the QNX 2 migration library that corresponds to the specified memory model (see option -m). The QNX 2 migration library provides backwards compatibility for many discontinued functions. The library is searched before the beta and standard libraries.

-b

Search the beta library that corresponds to the specified memory model (see option -m).

The beta libraries are searched before the standard libraries. The beta libraries include updates made since the last formal release of the software and can be updated by modem using the QNX update system.

-c

Suppress the link phase and retain all created object files.

-D name=text

Define name as if by a C language #define directive. If no text is specified, name is defined as 1.

-E

Copy the language source files to the standard output, expanding all preprocessor directives. No compilation is performed. See also option -P.

-F

Force objects into the same directory as source (default is the current working directory).

-f {option}

Pass through to the -f option of wcc.

-g{1|2}

Produce symbolic information in the object and executable files. This option is necessary to run the symbolic debugger (wd). If -g1 is specified, the optimizer remains enabled for code generation. If -g2 is specified, the optimizer is disabled, resulting in code that is easier to debug. Specifying -g is the same as specifying -g2.

-I directory

Change the default search algorithm for header files whose names don't begin with a slash (/) so that the directory named by the directory pathname is searched before the standard path. The standard path is /usr/include. Headers are searched for in the following order:

1. in the directory of the file with the #include line
2. in the directories named in the -I option
3. in /usr/include

Directories named with the -I option are searched in the order specified. If an #include is surrounded by angle brackets ( <> ), the first search isn't done.

-j

Change char default from unsigned to signed.

-L directory

Change the default algorithm (that searches for libraries) to include this directory. Directories are searched in the order they appear on the command line and before the default directory, /usr/lib. You may change this default by setting the environment variable LIBQNX to one or more directories separated by colons.

-l library

(the letter “el”) Search this library file for any unresolved references during the link phase. Libraries are searched in the order they appear on the command line, and before the default libraries. If the library name doesn't start with a slash (/), a search is made in the following order:

1. in the current directory
2. in the directories named in the -L option
3. in the default directory

If the library name doesn't end with .lib, the compilation-model suffix is appended.

-M

Produce a symbolic map file with the same name as the output file, but with a .map suffix.

-m{s|c|m|l|h|f}

Compile the program to conform to the specified memory model:

Option	Model	16-bit	32-bit
ms	small	64K code, 64K data	4G code, 4G data
mc	compact	64K code, >64K data	N/A
mm	medium	>64K code, 64K data	N/A
ml	large	>64K code, >64K data	N/A
mh	huge	>64K code, >64K data with objects >64K	N/A
mf	flat	N/A	4G code, 4G data

The small memory model is selected by default. For 16-bit applications, libraries are provided for the small, compact, medium, large, and huge memory models.

For 32-bit applications, only small-model libraries are provided and only small-model compiling is supported. However, cc does permit 32-bit small-model object modules to be linked as either small or flat models (flat-model linking is the default).

-N stacksize

Tell the linker to reserve room for a stack of stacksize bytes. The defaults are:

Model	Stacksize (K)
32-bit flat	32
32-bit small	8
16-bit	4

-O{a,d,e,f,f+,i,l,m,r,s,t,x}

Enable compiler optimizations. If only -O is specified, the default is equivalent to -Oil. You may specify more than one optimization by providing multiple letters together with no space or punctuation (for example, -Oadx).

-Oa

Relax alias checking. When you specify this option, the code optimizer assumes that, within the same routine, no variable is indexed both directly by name and indirectly by a pointer. This assumption may reduce the size of the code that is generated. The following example helps to illustrate this point:

extern int i;
void rtn( int *pi ) {

    int k;
    for( k = 0; k < 10; ++k ) {
        (*pi)++;
        i++;
    }
}

In this example, if i and *pi referenced the same integer object, i would be incremented by 2 each time through the for loop. The pointer reference *pi would be an alias for the variable i. As a result, in binding the variable i to a register, the compiler would have to make sure the “in-memory” copy of i was kept up-to-date. It's unlikely this situation would arise, since you probably wouldn't reference the same variable directly by name and indirectly by a pointer. The -Oa option instructs the code generator that such cases don't arise in the module to be compiled. When the generator doesn't have to worry about the alias problem it can produce more efficient code.

-Od

Generate non-optimized code sequences. The resulting code is much easier to debug with wd (see the Debugger User's Guide). By default, cc selects -Od if you specify option -g. But if option -g is followed by one of the other -O options, as in:

    cc -g -Os report

the default -Od is overridden.

-Oe=[number_of_quads]

Expand certain user functions inline. Whether a function is selected for inline expansion depends on its size, as measured by the number of quads the function generates. The number of quads generated corresponds closely to the number of operators used in an expression. Functions that require more than the specified number_of_quads aren't expanded inline (the default number is 20). This optimization is useful when locally referenced functions are small in size.

Example:

    cc -Oe dhrystone
    cc -Oe=25 whetstone

-Of

Generate traceable stack frames for functions that contain calls or require stack frame setup. For near functions, cc generates the following function prologue sequence:

16-bit compiler	32-bit compiler
push BP	push EBP
mov BP, SP	mov EBP, ESP

For far functions, cc generates the following function prologue sequence:

16-bit compiler	32-bit compiler
inc BP	inc EBP
push BP	push EBP
mov BP,SP	mov EBP,ESP

The BP/EBP value on the stack is odd or even, depending on the code model.

-Of+

Generate traceable stack frames for all functions, including those that don't contain calls or require stack frame setup. You should find this useful for developing embedded systems (ROM-based applications).

The f+ flag generates prologue sequences in the same way as the f flag.

-Oi

Generate certain library functions in-line. For a function to be generated in-line, you must include the appropriate header file containing the prototype for the function. These are the functions that can be generated in-line: abs()
_disable()
div()
_enable()
fabs()
_fmemchr()
_fmemcmp()
_fmemcpy()
_fmemset()
_fstrcat()
_fstrcmp()
_fstrcpy()
_fstrlen()
labs()
ldiv() (32)
lrotl() (32)
lrotr() (32)
inp()
inpw()
memchr()
memcmp()
memcpy()
memset()
movedata()
outp()
outpw()
_rotl()
_rotr()
strcat()
strchr()
strcmp()(16) strcpy()
strlen()

A (16) indicates that the function is generated inline by the 16-bit compiler only; a (32) indicates that it's generated inline by the 32-bit compiler only.

If you specify -Oi, the macro __INLINE_FUNCTIONS__ is predefined by the compiler.

-Ol

(lowercase letter “el”) Perform loop optimizations. This includes moving loop-invariant expressions outside the loops.

-Om

Generate inline 80x87 code for math functions such as sin(), cos(), tan(), and so on. If you specify this option, you must ensure that arguments to these functions fall within the range accepted by their corresponding instructions (for example, fsin, fcos) since no check is made at runtime.

If you also specify Ot, the exp() function is generated as well.

-Or

Enable reordering of instructions to achieve better performance on pipelined architectures such as the 486 and the Pentium. This option can make debugging a bit more difficult because the assembly language instructions generated for a source statement may be intermixed with instructions generated for surrounding statements.

-Os

Favor space over time when generating code. This results in smaller code but possibly slower execution.

-Ot

Favor time over space when generating code. This results in faster execution but possibly larger code.

-Ox

Select the -Oi, -Ol, and Wc,-s (no stack overflow checking) options. When you combine -Ox with the -Oa and -Ot options, the code generator attempts to give you the fastest executing code possible.
By default, cc selects a balance between space and time.

-o outfile

Use the pathname outfile instead of the default a.out for the executable file. If the -c option is also specified, outfile is taken to be the name of an object file to create.

-P

Run only the C preprocessor and leave the output in the same name as the source file but with an .i suffix. See also option -E.

-Q

Compile more quietly without printing the details of each compiler phase.

-S

Produce assembly-list files ending in .S for all source or object files provided. If an object file is specified, the original source lines won't be included in the generated assembly.

-s

Strip symbolic information that may exist in object files compiled with the -g option. The symbolic information isn't removed from these object files, but the resulting executable file is stripped of all symbolic information.

-T level

Set the privity level of the load file, where level can be a number from 0 to 3 (default is 3). A setting of T 1 is required for programs using in, out, cli, and sti. For more information, see the Description.

-U name

Remove any initial definition of name that the compiler itself might define. This doesn't affect any names defined in included header files.

-v version[@version_file]

Use this version of the compiler. The cc utility looks up the version supplied in the file /etc/default/cc, unless @version_file is specified, in which case the version information is looked up in that file instead. The version file (/etc/default/cc or the file specified) consists of entries that look like:

version_string
<tab>bins=directory_path
<tab>hdrs=directory_path
<tab>libs=directory_path
[ccopts=cc_options]
...
     

where the version_string is the version name cc is to recognise, and a directory_path is search path delimited by colons (:), such as “directory1:directory2”. The ccopts= cc_options is optional. It may be used to specify additional command line parameters to cc that are to be used for that version of the compiler. A typical entry might look like:

10.6
  bins=/usr/watcom/10.6/bin
  hdrs=/usr/watcom/10.6/usr/include:/usr/include
  libs=/usr/watcom/10.6/usr/lib:/usr/lib
     

-W c,option

Pass the command specified by option to the language processor, as specified by the c argument. The language processor is typically the letter c for the C language. You may specify c as one of the following:

For this processor:	specify:
assembler	s
C compiler	c
C++ compiler	C
disassembler	d (used in conjunction with -S)
linker	l
preprocessor	p (used in conjunction with -E or -P)
SQL preprocessor	S

If option contains a space, you must enclose the entire option in double quotes (for example, "-Wc,-xfile1").

The command specified by option is defined by the language processor being used. Please refer to the appropriate documentation.

-w warning_level

Use this warning level. If -w isn't specified, the built-in default for the language processor is used.

-X

Print, but don't execute, the steps required to compile or link.

-x

Use an experimental version of the compiler tools. Each command is invoked with a leading x (for example, wcc would be invoked as xwcc).

-z{option}

Pass through to the -z option of the C or C++ compiler.

Examples:

Compile test.c and create a 32-bit executable program in the current directory with the name a.out:

    cc test.c

Compile test.c and create a 32-bit executable program in the current directory with the name test:

    cc -o test test.c

Compile test.c and create an executable program in the current directory with the name test. Use the default rules to invoke cc (see the make utility in the QNX Utilities Reference):

    make test

Compile test.c and create a 16-bit object file in the current directory with the name test.o:

    cc -2 -c test.c

Disable stack overflow checking by passing the -s option to the C compiler:

    cc -Wc,-s test.c

Description:

The cc utility is the QNX compiler interface. It's based on the POSIX c89 utility.

The cc utility takes a list of source and object modules on the command line and invokes the appropriate parser to compile each file. Object modules are passed straight through to the linker. The file suffix determines which parser is used, as follows:

The cc utility doesn't allow multiple options to be specified after a dash character (-). For example, -bc isn't valid; you must specify -b -c instead. Operands (source and object files) and options may be mixed and specified in any order. Some options like -I and -L are order-dependent — the order in which they appear in the command line determines the order of the searches made. All command-line arguments are processed before any compilation or linking begins.

When cc encounters a compilation error that stops an object file from being created, it writes a diagnostic to the standard error and continues to compile other source files, but it bypasses the link phase and returns a nonzero exit status. If any file generates warnings or errors, and standard error is a tty (that is, it isn't a pipe), a new file is created with the same name as the input file but with a .err suffix. If the link phase is entered and is unsuccessful, a diagnostic is written and cc exits with a nonzero status.

The -c option suppresses the link phase. If you have many separate source files that you must update and modify individually, you'll probably use the -c option frequently.

In QNX, a program can run at one of the privity levels in the following table. The -T option lets you set the privity.

With level 0, the privity of the program is automatically set when the program is loaded. If the program is invoked by the superuser, its privity is set to 1; if the program is invoked by a normal user, its privity is set to 3. You should find this feature useful if your program needs to do in/out opcodes only when it is run by a superuser.

If a program is set to privity level 1, any attempt to execute that program by a non-superuser results in denied access.

Although you must be a superuser to execute privity level 1 programs, privity and superuser are two different concepts. The concept of superuser comes from POSIX, while privity relates only to Intel 286, 386, 486, and Pentium processors and allows or disallows a small set of opcodes.

If you link a program under QNX 4.1 (or later), its privity defaults to 3. If you find this program terminates with a SIGSEGV, check to see if it faults on one of the special opcodes that require privity level 1. If so, you should relink using the -T 1 option.

You may occasionally wish to examine the assembly code produced by the code generator. The -S option produces an assembly file ending in .S. You can also take an object file and convert it back to assembly with this option.

If you need to specify a parameter to any of the language processors, you may use the -W c,option. Check the documentation on each processor to determine its options.

The table below describes how the options for the cc command correspond to those for the Watcom C/C++ compiler and linker:

Exit status:

0

Successful completion.

>0

An error occurred.

Environment variables:

LIBQNX

The list of library directories to search-directories are separated by colons. If LIBQNX isn't defined, cc uses /usr/lib. If LIBQNX is defined, it's used as is.

Files:

The default output file is named a.out. This default may be changed with the -o option.

    make file1

See also:

lex utility (Lexical analyzer generator), make utility (Maintain, update and regenerate groups of programs), yacc utility (Parser generator), Watcom Compiler & Tools User's Guide