16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Examples<br />

–Uname<br />

Undefines a C or C++ macro specified with name. This option affects only<br />

macros defined by the –D option, including those automatically specified by<br />

c89/cc/c++. For information about macros that c89/cc/c++ automatically<br />

define, see Usage Note 2. Also see Usage Note 3.<br />

–Wphase,option[,option]...<br />

Specifies options to be passed to the steps associated with the compile,<br />

assemble, or link-editing phases of c89/cc/c++. The valid phase codes are:<br />

0 Specifies the compile phase (used for both non-IPA and IPA<br />

compilation).<br />

c Same as phase code 0.<br />

I Enables IPA (Interprocedural Analysis) optimization.<br />

Note: I is an uppercase i, not a lowercase L.<br />

Unlike other phase codes, the IPA phase code I does not require<br />

that any additional options be specified, but it does allow them. In<br />

order to pass IPA suboptions, specify those suboptions using the<br />

IPA phase code. For example, to specify that an IPA compile should<br />

save source line number information, without writing a listing file,<br />

specify:<br />

c89 -W I,list file.c<br />

To specify that an IPA link-edit should write the map file to stdout,<br />

specify:<br />

c89 -W I,map file.o<br />

Note: c89/cc/c++ options other than the ones listed will be ignored by<br />

makedepend.<br />

Any compiler option can be passed to makedepend through the –W option. For<br />

further information on the compiler options, refer to the z/<strong>OS</strong> XL C/C++ User’s<br />

Guide.<br />

1. makedepend file1.c file2.c<br />

Imagine you are compiling two files, file1.c and file2.c, and each includes the<br />

header file header.h. The header.h file includes the files def1.h and def2.h.<br />

When you run the command makedepend file1.c file2.c, makedepend parses<br />

file1.c and consequently, header.h, and then def1.h and def2.h. It then decides<br />

that the dependencies for this file are:<br />

v file1.o: header.h def1.h def2.h<br />

v file2.o: header.h def1.h def2.h<br />

2. Imagine you are compiling a file, file1.c, and it includes the header file header.h.<br />

The header.h file includes the files def1.h and def2.h. When you run the<br />

command makedepend file1.c, makedepend parses file1.c and consequently,<br />

header.h, and then def1.h and def2.h. It then decides that the dependencies for<br />

this file are:<br />

file1.o: header.h def1.h def2.h<br />

makedepend<br />

Chapter 2. Shell command descriptions 417

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!