digitalmars.com
Last update Sun Aug 7 02:11:45 2022
Compiler & Tools Guide
Tools
BCC
CHMOD
CL
COFF2OMF
COFFIMPLIB
DMC
DIFF
DIFFDIR
DMAN
DUMP
DUMPOBJ
DUMPEXE
EXE2BIN
FLPYIMG
GREP
HC
HTOD
IMPLIB
LIB
LIBUNRES
MAKE
MAKEDEP
ME
OBJ2ASM
PATCHOBJ
RC
RCC
SC
SHELL
SMAKE
TOUCH
UNMANGLE
WHEREIS
Compiling
Compiling Code
C Implementation
C++ Implementation
C++0x Implementation
Language Extensions
Mixing Languages
Assembly Language
Inline Assembler
Optimizing Code
Numerics Programming
Regular Expressions
Acrtused
Pragmas
Precompiled Headers
Predefined Macros
Warning Messages
Error Messages
Runtime Messages
Linking
Optlink
Switches
Module Definition Files
Operation and Design
Error Messages
Win32 Programming
Win32 Programming
DOS and Win16 Programming
Memory Models
16 Bit Pointer Types and Type Modifiers
Handle Pointers
DOS
DOS 32 (DOSX)
Win16
Win16 DLLs
Win16 Prolog/Epilog
Virtual Memory For 640Kb DOS
C/C++ Extensions
Contract Programming
__debug statement
__debug declaration
Dynamic Profiling
Embedding C in HTML
Porting to DMC++
Switching to DMC++
from Microsoft
from Borland
Porting Guide
<h1><a name="sc">DMC: Compiler</a> </h1> <p><strong>dmc</strong> is a one-step program to compile and link C++, C and ASM files. <strong>sc</strong> is the same program with a different name, kept for backwards compatibility. </p> <ul> <li><a href="#overview">Overview</a> <li><a href="#scdotini">sc.ini</a> <li><a href="#searches">How <tt>dmc.exe</tt> Searches For Programs</a> <li><a href="#environment">Environment Variables</a> <li><a href="#parameters">Parameters</a> <ul> <li><a href="#response"><strong>@</strong><em>responsefile</em></a> Response files <li><a href="#file"><em>file</em></a> Source file name <li><a href="#switches">Switches</a> <ul> <li><a href="#dasha"><strong>-a</strong></a> Set alignment of struct members <li><a href="#dashCapA"><strong>-A</strong></a> Standard C/C++ conformance <li><a href="#dashCapA"><strong>-A89</strong></a> ANSI X3.159-1989 conformance <li><a href="#dashCapA"><strong>-A90</strong></a> ISO/IEC 9899:1990 conformance <li><a href="#dashCapA"><strong>-A94</strong></a> ISO/IEC 9899-1:1994 conformance <li><a href="#dashCapA"><strong>-A95</strong></a> Same as <strong>-A94</strong> <li><a href="#dashCapA"><strong>-A99</strong></a> ISO/IEC 9899:1999 conformance <li><a href="#dashCapAa"><strong>-Aa</strong></a> Overload operators new[] and delete[] <li><a href="#dashCapAb"><strong>-Ab</strong></a> Enable bool as built-in type <li><a href="#dashCapAd"><strong>-Ad</strong></a> Revert to single level name lookup <li><a href="#dashCapAe"><strong>-Ae</strong></a> Enable exception handling <li><a href="#dashCapAr"><strong>-Ar</strong></a> Enable RTTI <li><a href="#dashCapAw"><strong>-Aw</strong></a> Enable wchar_t as a built-in type <li><a href="#dashCapB"><strong>-B</strong></a> Print error messages in other languages <li><a href="#dashc"><strong>-c</strong></a> Compile only, do not link executable. <li><a href="#dashcpp"><strong>-cpp</strong></a> Assume source files are C++ <li><a href="#dashCapC"><strong>-C</strong></a> Disable inline function expansion <li><a href="#dashcod"><strong>-cod</strong></a> Generate .cod (assembler output) file <li><a href="#dswitch"><strong>-d</strong></a> Generate dependency information <li><a href="#dashCapD"><strong>-D</strong></a> Define macro <li><a href="#dashe"><strong>-e</strong></a> Show results of preprocessor <li><a href="#dashCapECapC"><strong>-EC</strong></a> Do not elide comments <li><a href="#dashCapECapD"><strong>-ED</strong></a> Emit #defines to stdout (sppn only) <li><a href="#dashCapECapL"><strong>-EL</strong></a> #line directives not output <li><a href="#dashf"><strong>-f</strong></a> Generate IEEE 754 inline 8087 code <li><a href="#dashfd"><strong>-fd</strong></a> Generate IEEE 754 inline 8087 code with workaround for FDIV bug <li><a href="#dashff"><strong>-ff</strong></a> Generate fast inline 8087 code <li><a href="#dashg"><strong>-g</strong></a> Generate debug info <li><a href="#dashgg"><strong>-gg</strong></a> Make static functions global <li><a href="#dashgp"><strong>-gp</strong></a> Generate pointer validation code <li><a href="#dashgt"><strong>-gt</strong></a> Instrument for Dynamic Profiler <li><a href="#dashCapGCapT"><strong>-GT</strong></a> Set data threshhold <li><a href="#dashCapH"><strong>-H</strong></a> Use precompiled headers <li><a href="#dashCapHCapC"><strong>-HC</strong></a> Do not cache precompiled headers in memory <li><a href="#dashCapHCapD"><strong>-HD</strong></a> Set precompiled header directory <li><a href="#dashCapHCapF"><strong>-HF</strong></a> Write precompiled header to file <li><a href="#dashCapHCapH"><strong>-HH</strong><em>filename</em></a> Read precompiled header from <em>filename</em> <li><a href="#dashCapHCapI"><strong>-HI</strong></a> Include header file <li><a href="#dashCapHCapM"><strong>-HM</strong><em>address</em></a> Set address for memory mapped files <li><a href="#dashCapHCapO"><strong>-HO</strong></a> Include header files only once <li><a href="#dashCapHCapP"><strong>-HP</strong><em>nn</em></a> Set size of memory pool in megabytes <li><a href="#dashCapHCapS"><strong>-HS</strong></a> Only search -I for included header files <li><a href="#dashCapHCapX"><strong>-HX</strong></a> Use automatic precompiled headers <li><a href="#dashCapI"><strong>-I</strong></a> Set search path for include files <li><a href="#dashj"><strong>-j</strong></a> Asian language characters <li><a href="#dashCapJb"><strong>-Jb</strong></a> Disable empty base class optimization <li><a href="#dashCapJm"><strong>-Jm</strong></a> Relaxed type checking <li><a href="#dashCapJu"><strong>-Ju</strong></a> Char and unsigned char are the same type (unsigned char) <li><a href="#dashCapJ"><strong>-J</strong></a> Char promotions are unsigned <li><a href="#dashl"><strong>-l</strong></a> Generate source listing file <li><a href="#dashCapL"><strong>-L</strong></a> Using non-Digital Mars linker <li><a href="#dashCapLlinker"><strong>-L</strong><em>linker</em></a> Use linker <em>linker</em> instead of default. <li><a href="#dashCapLslash"><strong>-L/</strong><em>switch</em></a> Pass <strong>/</strong><em>switch</em> to linker. <li><a href="#dashCapM"><strong>-M</strong><em>asm</em></a> Specify assembler to use <li><a href="#dashCapMslash"><strong>-M/</strong><em>switch</em></a> Pass <strong>/</strong><em>switch</em> to assembler <li><a href="#switch_mn"><strong>-m</strong></a> Select memory model <li><a href="#dashCapNc"><strong>-Nc</strong></a> Function level linking <li><a href="#dashCapNCapC"><strong>-NC</strong></a> Don't generate COMDATs (obsolete) <li><a href="#dashCapNCapD"><strong>-ND</strong></a> Compile and link with DLL version of runtime library <li><a href="#dashCapNCapF"><strong>-NF</strong></a> Ignore extended keywords <li><a href="#dashCapNCapL"><strong>-NL</strong></a> Do not embed default library record <li><a href="#dashCapNCapL"><strong>-NL</strong><em>libfile</em></a> Embed library <em>libfile</em> <li><a href="#dashCapNs"><strong>-Ns</strong></a> Place expression strings in code seg <li><a href="#dashCapNCapS"><strong>-NS</strong></a> New code seg for each function <li><a href="#dashCapNt"><strong>-Nt</strong></a> Use old template name mangling scheme (obsolete) <li><a href="#dashCapNCapT"><strong>-NT</strong></a> Set code segment name <li><a href="#dashCapNCapV"><strong>-NV</strong></a> Put virtual function tables in far data segments. <li><a href="#dasho"><strong>-o</strong></a> Run optimizer <li><a href="#dashoSPP"><strong>-o</strong></a> SPP only: send result to stdout <li><a href="#dashofilename"><strong>-o</strong><em>filename</em></a> Specify output <em>filename</em> <li><a href="#dashp"><strong>-p</strong></a> Turn off autoprototyping <li><a href="#dashCapP"><strong>-P</strong></a> Default to pascal linkage <li><a href="#dashCapPdash"><strong>-P-</strong></a> Default to cdecl linkage <li><a href="#dashCapPz"><strong>-Pz</strong></a> Default to stdcall linkage <li><a href="#dashr"><strong>-r</strong></a> Strict prototyping <li><a href="#dashCapR"><strong>-R</strong></a> Put switch tables in code segment <li><a href="#dashs"><strong>-s</strong></a> Stack overflow checking <li><a href="#dashCapS"><strong>-S</strong></a> Always generate stack frame <li><a href="#dashu"><strong>-u</strong></a> Suppress predefined macros <li><a href="#dashv"><strong>-v</strong></a> Verbose compile <li><a href="#dashw"><strong>-w</strong></a> Warning messages <li><a href="#dashwc"><strong>-wc</strong></a> Warn on C style casts <li><a href="#dashwx"><strong>-wx</strong></a> Treat warnings as errors <li><a href="#dashCapW"><strong>-W</strong></a> Windows prolog/epilog <li><a href="#dashx"><strong>-x</strong></a> Turn off compilation error maximum <li><a href="#dashCapXCapD"><strong>-XD</strong></a> Instantiate template for any functions declared but not defined <li><a href="#dashCapXCapI"><strong>-XI</strong></a> Create instance of template <li><a href="#dashCapXCapN"><strong>-XN</strong></a> No template function instantiation <li><a href="#dash023456"><strong>-[0|2|3|4|5|6]</strong></a> 88/286/386/486/P5/Pro code </ul> </ul> </ul> <h3><a name="overview">Overview</a> </h3> <p>Arguments to DMC can be presented in any order, if any arguments conflict, the rightmost argument takes precedence. The command line to DMC takes the form: </p> <pre><strong>dmc</strong> { { <strong>@</strong><em>responsefile</em> } { <em>file</em> } { <em>switches</em> } } </pre> <p>where the { } means "repeated 0 or more times". DMC with no arguments prints a short help file to stdout. </p> <h3><a name="scdotini">sc.ini</a> </h3> <p>DMC looks in the directory where <tt>dmc.exe</tt> resides for the file <strong>sc.ini</strong>. <strong>sc.ini</strong> is a text file, containing environment variable settings in a similar manner as they might be set in AUTOEXEC.BAT: </p> <pre>;Comments are lines where the first non-blank ;character is a ';' [Environment] INCLUDE=c:\dm\bin LIB=c:\dm\lib CFLAGS=-v -w ;Note that %PATH% gets replaced by the previous ;value of the environment variable PATH. PATH=c:\dm\bin;%PATH% </pre> <p>The special environment variable <strong>@P</strong> gets replaced with the path to where the <strong>sc.ini</strong> file resides. For instance, the above can be replaced with (if <strong>sc.ini</strong> is in <tt>c:\dm\bin</tt>): </p> <pre>[Environment] INCLUDE=%@P%..\BIN LIB=%@P%..\LIB CFLAGS=-v -w PATH=%@P%..\BIN;%PATH% </pre> <p>which makes the settings in <strong>sc.ini</strong> independent of where the DMC directory tree is installed. </p> <p>If <strong>sc.ini</strong> is not there, no error results. This feature is useful for avoiding cluttering up AUTOEXEC.BAT with environment variable settings. Not only that, it will make running DMC independent of any existing environment variables set for other tools. </p> <p>The environment settings in <strong>sc.ini</strong> do not prefix, augment, or append any existing settings in the environment. They replace the environment settings for the duration of running the IDDE or the compiler. For example, to use <strong>sc.ini</strong> to append an INCLUDE path to the existing INCLUDE path, it can be written as: </p> <pre>[Environment] INCLUDE=%INCLUDE%;c:\dm\include </pre> <h3><a name="searches">How DMC.EXE Searches For Programs</a> </h3> <p>DMC first searches in the directory from where DMC.EXE was found. If the programs are not found there, then the PATH is searched. </p> <h3><a name="environment">Environment Variables</a> </h3> <p>DMC uses the following environment variables, either set at the console command line prompt or in the file <strong>sc.ini</strong>: </p> <dl> <dt><strong>CFLAGS</strong></dt> <dd>If it is set, it behaves as if the first argument to DMC is <strong>@CFLAGS</strong>. <strong>CFLAGS</strong> is a convenient way to temporarily set switches to the compiler without modifying batch files or makefiles. </dd> <dt><strong>INCLUDE</strong></dt> <dd>Path to search for #include'd files. </dd> <dt><strong>LIB</strong></dt> <dd>Search path for library files. </dd> <dt><strong>PATH</strong></dt> <dd>Search path for executable files if they are not found in the same directory where DMC resides. </dd> </dl> <h3><a name="parameters">Parameters</a> </h3> <dl> <dt><a name="response"><strong>@</strong><em>responsefile</em></a> </dt> <dd><em>responsefile</em> is searched for as an environment variable name, and if not found, as a file name. If it is found, the text of the environment variable or file name is inserted in the command line as if it were part of the command line. In this way, the command line length limit of many operating systems can be circumvented. If <em>responsefile</em> is not found, no text is inserted. </dd> <dt><a name="file"><em>file</em></a> </dt> <dd>A file name. If no extension is given, the following extensions are tried in the order given to see if there is a match: <ol><li>.c</li> <li>.cpp</li> <li>.cxx</li> <li>.cc</li> <li>.c++</li> <li>.asm</li> <li>.s</li> <li>.rc</li> </ol> <p>The extension of the file determines what is done with the file.</p> <table class="structure"><tr><th>Extension</th> <th>Action</th></tr> <tr><td><em>no extension</em></td> </tr> <tr><td><em>any other extension</em></td> </tr> <tr><td>.c</td> <td>Run C compiler</td></tr> <tr><td>.cpp</td> </tr> <tr><td>.cxx</td> </tr> <tr><td>.cc</td> </tr> <tr><td>.c++</td> <td>Run C++ compiler</td></tr> <tr><td>.asm</td> </tr> <tr><td>.s</td> <td>Run assembler</td></tr> <tr><td>.lib</td> </tr> <tr><td>.a</td> <td>Include file as a library to the linker</td></tr> <tr><td>.obj</td> </tr> <tr><td>.o</td> <td>Include file as an object file to the linker</td></tr> <tr><td>.exe</td> </tr> <tr><td>.com</td> </tr> <tr><td>.sys</td> </tr> <tr><td>.dll</td> <td>Include file as the output file to the linker</td></tr> <tr><td>.def</td> <td>Include file as the module definition file to the linker</td></tr> <tr><td>.rc</td> <td>Run resource compiler</td></tr> <tr><td>.res</td> <td>Include file as the resource file to linker</td></tr> </table> </dd> </dl> <h3><a name="switches">Switches</a> </h3> <dl> <dt><a name="dasha"><strong>-a[-|1|2|4|8]</strong></a> </dt> <dd>Set alignment of struct members. <dl> <dt> <strong>-a, -a1</strong></dt> <dd>align on byte boundaries</dd> <dt> <strong>-a-</strong></dt> <dd>(default) use alignment indicated by selection of memory model</dd> <dt> <strong>-a2</strong></dt> <dd>align on 2 byte boundaries (default for 16 bit models)</dd> <dt> <strong>-a4</strong></dt> <dd>align on 4 byte boundaries (default for DOSX)</dd> <dt> <strong>-a8</strong></dt> <dd>align on 8 byte boundaries (default for Win32)</dd> </dl> <p>Alignment can also be controlled within a source file by using #pragma pack(). </p> </dd> <dt><a name="dashCapA"><strong>-A</strong></a> </dt> <dd><p>Strict ANSI C/C++, which disables all non-ANSI extensions. This is useful for compiling ANSI test suites, and for verifying that code will compile in a strict ANSI environment.</p> <p>Effects on C and C++:</p> <ul> <li> Predefined macros that do not start with a single or double underscore are not defined. <li> The macro __STDC__ is defined and set to 1. <li> Trigraphs are enabled. <li> Floating point comparison operators <>=, !<>=, <>, !>, !>=, !< !<= !<> are disabled. <li> Binary integer constants (such as 0b10110) are disabled. <li> Keywords beginning with a single _ are disabled. <li> asm, cdecl, far, huge, near, pascal keywords are disabled. <li> '$' is not allowed as an identifier character. <li> /p (pascal strings) are disabled. <li> At least one hex number must follow a \x escape sequence. <li> Hex numbers specified with a trailing h are disabled. <li> MASM-style hexadecimal constants (012h, 1E3H, etc.) are disallowed. <li> Blank macro arguments not allowed. <li> #defines that redefine macros must be preceded by #undefs <li> Arithmetic operations on function pointers are invalid <li> Text at the end of a preprocessor directive is an error, so, #endif COMMENT would need to be #endif /* COMMENT*/. <li> Empty member lists in enums, or member lists with a trailing comma (,) become syntax errors. <li> Casts and sizeof() are invalid in preprocessor expressions <li> #ident is disallowed. <li> The compiler no longer recognizes the following extended keywords: _asm, _cdecl, _declspec, _export, _far, _seg16, _fastcall, _fortran, _handle, _huge, _interrupt, _loadadds, _near, _pascal, _saveregs, _stdcall, _syscall. For ANSI compatibility, use the "__" (double-underscore) versions of these keywords. The versions of these keywords without leading underscores are also not recognized with -A. <li> It is an error to have an unrecognized preprocessor directive in a false conditional block. </ul> <p>Effects on C:</p> <ul> <li> Type checking on default integral promotions is more strict. <li> Source files must end with a newline character (\n). </ul> <p>Effects on C++:</p> <ul> <li> RTTI support is enabled. <li> Exception handling support is enabled. <li> overload keyword is disabled <li> implicit conversion of void* to pointers of other types is invalid <li> Syntax like <code>char abc[4] = "1234";</code> where there is no room for the trailing 0 is invalid. <li> Anonymous unions with file scope must be static <li> Member functions can't be declared as static outside a class definition <li> static class data members must be defined somewhere in the program source. <li> Overloading of operator new[] and operator delete[] is enabled. <li> Floating types for non-type template-parameters are disallowed. </ul> </dd> <dt><strong>-A-</strong></dt> <dd>turn off <strong>-A</strong></dd> <dt> <a name="dashCapAa"><strong>-Aa</strong></a> </dt> <dd>Enable overloading of operator new[] and operator delete[] separate from operator new and operator delete. This also predefines the macro _ENABLE_ARRAYNEW. -A (ANSI compatibility) also enables -Aa. </dd> <dt> <a name="dashCapAb"><strong>-Ab</strong></a> </dt> <dd>enable bool as a built-in type, with values true and false </dd> <dt> <a name="dashCapAd"><strong>-Ad</strong></a> </dt> <dd>Revert to single level name lookup, as opposed to the standard conforming two level lookup. </dd> <dt> <a name="dashCapAe"><strong>-Ae</strong></a> </dt> <dd><p>Enable exception handling</p> <p>Because code generated for exception handling (EH) is not quite as good ('this' pointers are not placed in registers, tables are generated), the default is that EH is not enabled. To enable EH, compile with the -Ae switch. Compiling for ANSI C++ (-A) will also enable exception handling support. </p> <p>To compile C code that is to be mixed into C++ code that handles exceptions, compile the C code with -Ae also. </p> <p>Objects compiled with -Ae may be linked with objects compiled without -Ae, provided that no exceptions are thrown in the resulting program that are not handled entirely within objects compiled with -Ae. </p> <p>The tables are generated in the same segment using the same rules as the virtual function pointer tables. Using -NV will place the tables in far segments (for 16 bit memory models). </p> </dd> <dt><a name="dashCapAr"><strong>-Ar</strong></a> </dt> <dd><p>Enable RTTI (Run Time Type Identification) support. RTTI is off by default because RTTI adds space and time to executables. RTTI works by adding a new member to the virtual function table (vtbl[]), a pointer to the type info for that struct. This means that classes can no longer share vtbl[]s (an optimization done by default). The type info pointer is at a negative offset to the start of the vtbl[], this is to retain object model compatibility with the Microsoft Object Model (which does not support RTTI). </p> <p>For link compatibility with Microsoft C++ compiled DLLs, but still using RTTI, compile with <strong>-ER</strong>: </p> <ul> <li> All modules that use typeid() <li> All modules that use dynamic_cast <li> All modules that compile the bodies of constructors for classes that need to support RTTI </ul> <p>The reason for this is that the vptr member of the class needs to be set to a virtual function table that has the RTTI type info pointer in it. A vtbl[] with RTTI type info has a different mangled name than one without, this helps to get everything linked up right. </p> <p>Virtual function call compatibility is not affected by RTTI. </p> <p>It is best to avoid using RTTI on classes that are pulled in from a .LIB, .OBJ or .DLL where they were compiled with a different compiler. </p> </dd> <dt> <a name="dashCapAw"><strong>-Aw</strong></a> </dt> <dd>Enable wchar_t as a built-in type</dd> <dt> <strong>-bx</strong></dt> <dd>Run X versions of compiler passes (obsolete, ignored)</dd> <dt> <strong>-bn</strong> Run NT console app versions of compiler passes (obsolete, ignored)</dt> <dt><a name="dashCapB"><strong>-B, -Be, -Bf, -Bg, -Bj</strong></a> </dt> <dd>Causes compiler error messages to be printed in the various languages. This switch would be most conveniently be set in the CFLAGS environment variable or <strong>sc.ini</strong> file. <dl> <dt> <strong>-B</strong> English</dt> <dt> <strong>-Be</strong> English</dt> <dt> <strong>-Bf</strong> French</dt> <dt> <strong>-Bg</strong> German</dt> <dt> <strong>-Bj</strong> Japanese</dt> </dl> </dd> <dt> <a name="dashc"><strong>-c</strong> Compile only, do not link executable.</a> </dt> <dt><a name="dashcpp"><strong>-cpp</strong> Assume source files are C++</a> </dt> <dd>Causes DMC to run the C++ compiler rather than the C compiler on source files with a .c extension or an unrecognized extension. To separately precompile a .h file for C++, use the <strong>-cpp</strong> switch. </dd> <dt><a name="dashCapC"><strong>-C</strong> Disable inline function expansion</a> </dt> <dt><strong>-C-</strong> (default) enable inline expansion</dt> <dd><p>Prevents the inline expansion of functions with the inline storage class. This can be useful in sorting out a complex tangle of inlined functions when debugging. It can also result in smaller (but slower) generated executables. It has no effect on compiler intrinsic functions like strcmp() and memcpy(). If these functions should not be inlined, use the portable method:</p> <pre>#undef strcmp /* use runtime library version of strcmp */ </pre> </dd> <dt><a name="dashcod"><strong>-cod</strong> Generate .cod (assembler output) file</a> </dt> <dd>Causes <a href="/index.cgi/speech/https://digitalmars.com/ctg/obj2asm.html">obj2asm</a> to be run on the .obj file output from the compiler to generate a .cod file showing the assembly code generated. Using this along with the <strong>-gl</strong> switch will generate a mixed source/assembly .cod file. </dd> <dt><a name="dswitch"><strong>-d</strong> Generate dependency information</a> </dt> <dd><p>If <tt>file.c</tt> is being compiled, then <tt>file.dep</tt> will be created. It will contain a list of #include files that <tt>file.obj</tt> depends on. The line in the <a href="/index.cgi/speech/https://digitalmars.com/ctg/make.html">makefile</a> can be written as:</p> <pre>file.obj : $(file.dep) file.c dmc -c file -d </pre> </dd> <dt><a name="dashCapD"><strong>-D</strong>[<em>macro</em>[=<em>text</em>]] define macro</a> </dt> <dd> <dl> <dt><strong>-D</strong></dt> <dd>Equivalent to <tt>#define DEBUG 1</tt><br> Will also enable the <a href="/index.cgi/speech/https://digitalmars.com/ctg/debugstatement.html">debug statements</a> and <a href="/index.cgi/speech/https://digitalmars.com/ctg/debugstatement.html#debugdeclaration">debug declarations</a>. </dd> <dt><strong>-D</strong><em>macro</em></dt> <dd>Equivalent to <tt>#define <em>macro</em> 1</tt></dd> <dt><strong>-D</strong><em>macro</em>=</dt> <dd>Equivalent to <tt>#define <em>macro</em></tt></dd> <dt><strong>-D</strong><em>macro</em>=<em>text</em></dt> <dd>Equivalent to <tt>#define <em>macro</em> <em>text</em></tt></dd> </dl> <p>The '#' character can be used instead of '='. To embed white space in the macro's <em>text</em>, enclose the entire <em>text</em> in double ("") or single quotation marks (''), as in <tt>-Dmacro="this is a string"</tt>, which is equivalent to: </p> <pre>#define macro "this is a string" </pre> </dd> <dt><a name="dashe"><strong>-e</strong> show results of preprocessor</a> </dt> <dd>Shows the effects of the preprocessor in error messages and in the list file. To verify that macros are expanding as expected, use the options <strong>-e</strong> and <a href="#dashl">-l</a> together. </dd> <dt><a name="dashCapECapC"><strong>-EC</strong> do not elide comments</a> </dt> <dd>For SPP: leave comments in preprocessed output. </dd> <dt><strong>-EH</strong> obsolete - use <strong>-Ae</strong></dt> <dt><a name="dashCapECapL"><strong>-EL</strong> #line directives not output</a> </dt> <dd>For SPP: do not add #line directives into the output. </dd> <dt><strong>-ER</strong> obsolete - use <strong>-Ar</strong></dt> <dt><a name="dashf"><strong>-f</strong> generate IEEE 754 inline 8087 code</a> </dt> <dd><p>For 16 bit code and the DOSX memory model, the compiler by default generates code assuming a numeric coprocessor does not exist. This code is less efficient than if numeric coprocessor code is generated directly. <strong>-f</strong> will cause numeric coprocessor code to be generated directly, but the code will not run on machines without a coprocessor.</p> <p>Win32 implementations have an emulator for the numeric coprocessor, so <strong>-f</strong> is the default for the -mn memory model.</p> </dd> <dt><a name="dashfd"><strong>-fd</strong> generate IEEE 754 inline 8087 code with workaround for FDIV bug</a> </dt> <dd><p>Some old Pentium CPU chips have a <a href="https://en.wikipedia.org/wiki/Pentium_FDIV_bug">bug</a> when executing FDIV instructions. When not generating inline 8087 code, the floating point emulator in the runtime library automatically accounts and corrects for the errors. When generating inline 8087 code, the <strong>-fd</strong> switch will call a runtime library function for FDIV instead of generating an FDIV instruction directly. This results in code that is a little larger and slower than <strong>-f</strong> code, but it won't be subject to FDIV bugs. Do not use <strong>-fd</strong> if the code will never be run on a Pentium.</p> <p>No Pentium Pro or Pentium MMX chips have this bug.</p> </dd> <dt><a name="dashff"><strong>-ff</strong> fast inline 8087 code</a> </dt> <dd><p>The difference between <strong>-f</strong> and <strong>-ff</strong> is that with <strong>-ff</strong> floating point comparisons with NaN (Not a Number) are not done exactly according to IEEE 754. Normally, this does not matter, so <strong>-ff</strong> will yield faster code. Other compilers for Intel CPUs do not correctly generate code for NaN comparisons, so to compare Digital Mars floating point code performance with that of other compilers, use the <strong>-ff</strong> switch. </p> <p><strong>-ff</strong> will also cause the folding of floating point constants even if they would generate an exception. For example, 0.0/0.0 will be folded at compile time instead of at runtime. </p> <p>Use <strong>-ff</strong> <strong>-fd</strong> in combination to get fast inline code with the <a href="https://en.wikipedia.org/wiki/Pentium_FDIV_bug">FDIV bug</a> workaround.</p> </dd> <dt><a name="dashg"><strong>-g</strong>{<strong>-345dfghlpst</strong>} generate debug info</a> </dt> <dd><p>There are several ways of generating debug info for a compiled file. If the compiler always generated debug info for all types, the .OBJ files would be huge and the linker would have a lot of work to do to remove all the redundant information. Ideally, debug info is generated only once for each type across all compilation units. </p> <p>The default, <strong>-g</strong>, only generates debug info for types of variables that are actually used by a module. This greatly cuts down on the size of the object file. In addition, since C++ class hierarchies tend to be very complex, <strong>-g</strong> generates class debugging information only for classes for which a corresponding virtual function table is generated. </p> <p><strong>-g</strong> is the right choice for programs that do not reference libraries or DLL's for which type info is needed. </p> <p>Sometimes, though, if part of a class implementation lies inside a DLL, the debug info for that class may never get generated. Thus, the <strong>-gf</strong> flag exists to cause full debug info to be generated for each class that is reference by generated code. </p> <p>Even <strong>-gf</strong> can get a bit problematic, since it can cause large quantities of debug info to be generated. It also never generates debug info for classes that only may be referenced in a linked-in library or DLL which were compiled separately without debug info. </p> <p><strong>-gh</strong> causes debug info to be generated for all global structs and typedefs, regardless of if they are referenced or not. One could just use <strong>-gh</strong> for all compilations, and it will work, but it will be a bit slow. </p> <p>A better solution is to use <strong>-g</strong> for all the modules in the program. Then, create a special file TOTAL.C, which has a #include statement in it for each header that references a library or DLL. Compile TOTAL.C with <strong>-gh</strong> (and the other memory model, etc. switches), and TOTAL.OBJ will contain all the debug info needed for those DLLs and libraries. This will minimize compile/link times, which is important for fast development turnaround. </p> <p>OBJ2ASM can be run on any .OBJ file, and it will format and pretty-print any debug info found in the file. This is handy to see what the compiler is doing. </p> <dl> <dt><strong>-g</strong> Generate line info and debug info for types of referenced variables.</dt> <dd>Equivalent to -gsl. Type info for typedefs and enums is not generated. </dd> <dt><strong>-g-</strong> turn off debug output</dt> <dt><strong>-g3</strong> Generate Codeview 3 format debug info.</dt> <dd>This is useful to support old debuggers, but is now obsolete. It is no longer supported.</dd> <dt><strong>-g4</strong> Generate Codeview 4 format debug info.</dt> <dd>This is the default.</dd> <dt><strong>-g5</strong> Generate Digital Mars format.</dt> <dt><strong>-gd</strong> Dynamic C++ type info (obsolete)</dt> <dt><strong>-gf</strong> Generate debug info for full class hierarchy for any referenced classes.</dt> <dt><a name="dashgg"><strong>-gg</strong></a> Make static functions global.</dt> <dd><p>This is useful when tools that read .MAP files are needed, since only global function names will appear in the .MAP file. </p> <p>If a C++ inline function is outlined, it still remains static, even with the -gg option enabled. This is because name collisions in this case are difficult to prevent. A C++ inline function is outlined if: </p> <ul> <li> It is virtual. <li> The address of the function is taken. <li> The function cannot be reduced to a simple expression; that is, it contains do, while, for, or switch constructs. </ul> </dd> <dt><strong>-gh</strong> Generate debug info for all global structs, enums, and typedefs.</dt> <dd>This is done automatically if <strong>-g</strong> is thrown with <strong>-HF</strong>. </dd> <dt><strong>-gl</strong> Generate line number debug info only.</dt> <dd>This is useful when a .cod file output is desired, as then the source code will be intermixed in with the compiled output. It is also useful when working with debuggers that derive all their debug info from .MAP files. </dd> <dt><a name="dashgp"><strong>-gp</strong></a> generate pointer validations</dt> <dd><p>Generates code to call the function __ptrchk(void *p) for each pointer dereference. p is always a far pointer for 16 bit memory models, and always a near pointer for 32 bit memory models.</p> <p>__ptrchk must preserve all registers, and must pop its parameter prior to returning (pascal calling sequence). These measures minimize the code expansion resulting from using <strong>-gp</strong>. Thus, __ptrchk must be written in assembler or inline assembler. </p> <p>__ptrchk is intended for use by a memory debugger. The idea is that __ptrchk validates the pointer. If the pointer is not valid, it notifies the user at the source of the problem. </p> <p>There is a default version of __ptrchk in the runtime library.</p> </dd> <dt><strong>-gs</strong> symbol info only (do not generate line number info)</dt> <dt><a name="dashgt"><strong>-gt</strong></a> Generate trace prolog/epilog for use with the Digital Mars Trace package.</dt> <dd><p>Adds a call to a user-defined function to the prolog and epilog of each function. The function calls generated are:</p> <pre>void __far _trace_pro_n(void) // Prolog for near functions void __far _trace_pro_f(void) // Prolog for far functions void __far _trace_epi_n(void) // Epilog for near functions void __far _trace_epi_f(void) // Epilog for far functions </pre> <p>The code for these functions must be provided; typically, they would be used to generate debugging information to support profiling. The functions must preserve all registers and, therefore, must be in assembly language.</p> <p>The prolog function is called after the stack frame is set up, and the epilog is called just before the stack frame is destroyed.</p> <p>Implementations of these functions are provided in the runtime library that implement <a href="/index.cgi/speech/https://digitalmars.com/ctg/trace.html">dynamic execution profiling</a>.</p> </dd> </dl> <p>Different instances of <strong>-g</strong> can be combined sequentially. For example, <strong>-g3h</strong> is equivalent to "<strong>-g3 -gh</strong>." If combinations conflict, the compiler uses the last option specified. For example, <strong>-g -g4</strong> generates CV4 format information; <strong>-g4 -g3</strong> generates CV3 format information.</p> </dd> <dt><a name="dashCapGCapT"><strong>-GT</strong><em>nnnn</em> set data threshold to <em>nnnn</em></a> </dt> <dd><p>In large data models arrays and structs that are larger than <em>nnnn</em> are allocated in far data segments rather than DGROUP. </p> <dl> <dt><strong>-GT</strong><em>nnnn</em></dt> <dd>Allocate arrays and structs larger than <em>nnnn</em> to far data segments.</dd> <dt><strong>-GT</strong></dt> <dd>Default (all static data is placed in DGROUP).</dd> </dl> <p>The <strong>-GT</strong><em>nnnn</em> switch is ignored for near data models (t,s,m) and for all 32 bit memory models. </p> <p>If using <strong>-GT</strong>, use the same value for all modules. For .ASM modules, be careful when referencing global data whether it is in DGROUP or in a far data segment. The symptoms of getting this wrong are frame errors from the linker. </p> <p>Note that if <strong>-GT</strong> is used, arrays declared with empty [] like:</p> <pre>extern int array[]; </pre> <p>are assumed to be far. If they actually are near, declare them using the dimension, or mark them explicitly as <strong>__near</strong>.</p> <p>Always be sure to use the same <em>nnnn</em> threshold value for all modules compiled with <strong>-GT</strong>.</p> </dd> <dt><a name="dashCapH"><strong>-H</strong> use precompiled headers (ph)</a> </dt> <dd><p>When the compiler encounters a #include statement for filename.h, it looks instead for filename.sym in the current directory. filename.sym is the precompiled version of the header file. </p> <p><strong>-H</strong> also implies <strong>-HO</strong> (include files only once).</p> </dd> <dt><strong>-H-</strong> Do not use precompiled headers (default)</dt> <dt><a name="dashCapHCapC"><strong>-HC</strong> Do not cache precompiled headers in memory.</a> </dt> <dt><strong>-HC-</strong> Cache precompiled headers in memory (default).</dt> <dd><p>In the IDDE, by default, when precompiled headers are read in from disk, they are cached in memory so when subsequent files are compiled, the precompiled header is read from memory rather than from disk. When there is not a lot of physical memory, however, this can cause a lot of page swapping, resulting in decreased compile speeds. Thus, the <strong>-HC</strong> switch will turn off caching them. </p> <p>The <strong>-HC</strong> switch does not apply to <strong>-HX</strong> precompiled headers, which are always cached in memory for IDDE compiles. The <strong>-HC</strong> switch is ignored for the command line compiler, which always reads precompiled headers from disk.</p> </dd> <dt><a name="dashCapHCapD"><strong>-HD</strong><em>directory</em> Set precompiled header directory</a> </dt> <dd>If the precompiled header directory for use with the <strong>-H</strong>, <strong>-HF</strong> and <strong>-HX</strong> switches is not the current directory, use <strong>-HD</strong> to set the directory to use. This is useful when the precompiled headers go to a fast ram disk. </dd> <dt><a name="dashCapHCapF"><strong>-HF</strong>[<em>filename</em>[<strong>.sym</strong>]] write precompiled header to <em>filename</em><strong>.sym</strong>.</a> </dt> <dd><p><strong>-HF</strong> is used to generate a precompiled header, <strong>-H</strong> is used to compile files that will be using that precompiled header. The default output file name is the name of the source file with a <strong>.sym</strong> extension. </p> <p>The <em>filename</em><strong>.obj</strong> file that is also generated should be linked in as well, as contains code and data generated when building the precompiled header. If <strong>-g</strong> is thrown, the <strong>.obj</strong> file will contain all the debug info for the header file(s).</p> </dd> <dt><a name="dashCapHCapH"><strong>-HH</strong><em>filename</em> Read precompiled header from <em>filename</em>.</a> </dt> <dd>A precompiled header's filename is normally generated from the name of the first #include file. This switch will set an alternate file name to be used. </dd> <dt><a name="dashCapHCapI"><strong>-HI</strong><em>filename</em> #include <em>filename</em></a> </dt> <dd><p>Before compiling the source files on the command line, #include the file <em>filename</em> along with them. Using this option is like adding #include <em>filename</em> to the beginning of each source file in the compilation. </p> <p>This option is especially useful for including a precompiled header at the beginning of all the source files.</p> </dd> <dt><a name="dashCapHCapM"><strong>-HM</strong><em>address</em></a> </dt> <dd>Set address to use for memory mapped files. <em>address</em> is in hex. </dd> <dt><a name="dashCapHCapO"><strong>-HO</strong> Include header files only once</a> </dt> <dt><strong>-HO-</strong> (default) turn off <strong>-HO</strong></dt> <dd><p>Normally, include files are read and parsed each time they are encountered. With <strong>-HO</strong>, include files are read and parsed only the first time they are encountered, and #include directives for that file are ignored if they appear again. This can result in faster compiling. </p> <p>An alternative is to include the directive</p> <pre>#pragma once </pre> <p>in each include file that will never need to be parsed more than once.</p> </dd> <dt><a name="dashCapHCapP"><strong>-HP</strong><em>nn</em> Set size of memory pool in megabytes</a> </dt> <dd>Under rare cases, the compiler may exit with an message about being out of memory. The size of the memory pool can be set to <em>nn</em> megabytes with this switch. <em>nn</em> should be greater than 30. </dd> <dt><a name="dashCapHCapS"><strong>-HS</strong> only search <strong>-I</strong><em>path</em> directories</a> </dt> <dd>Directs the compiler to search for #included header files only along the path specified by the <a href="#dashCapI">-I</a> switch. The current directory and the directory specified by the <a href="#include">INCLUDE</a> environment variable are not searched. </dd> <dt><a name="dashCapHCapX"><strong>-HX</strong> Use automatic precompiled headers</a> </dt> <dd><p>Automatically generate and use a precompiled header named <tt>scph.sym</tt>. The precompiled header is generated if it does not exist or if any of the header files in it are newer than the <tt>scph.sym</tt> file. </p> <p>The <tt>scph.sym</tt> file is placed in the current directory by default. The <a href="#dashCapHCapD">-HD</a> switch sets an alternate directory for it.</p> </dd> <dt><a name="dashCapI"><strong>-I</strong><em>path</em> Set search path for include files</a> </dt> <dd><p>Searches for #include files along the specified path. Paths may end in a \. Multiple paths can be specified by separating them with a ';'. For example: </p> <table class="structure"> <tr> <th> Switch <th> Search <tr> <td> <tt>-Iabc</tt> <td> Subdirectory abc <tr> <td> <tt>-Id:</tt> <td> Default directory in drive d: <tr> <td> <tt>-Iabc;d:</tt> <td> Both of above directories <tr> <td> <tt>-Ig:\cbx\include\</tt> <td> Directory g:\cbx\include <tr> <td> <tt>-I.</tt> <td> Current directory <tr> <td> <tt>-I\</tt> <td> Root directory </table> </dd> <dt><a name="dashj"><strong>-j[0|1|2]</strong> Asian language characters</a> </dt> <dd><p>Asian language character sets include double byte characters, where certain prefix bytes mean that the following byte forms part of the character. Asian language characters can appear in "" strings, in '' character literals, and in comments. </p> <tr> <strong>-j, -j0</strong> Japanese <tr> <strong>-j1</strong> Taiwanese and Chinese <tr> <strong>-j2</strong> Korean <tr> <strong>-j-</strong> no Asian language characters <p>When the compiler is run under Win32, the switches correspond to the following operating system locale code pages: </p> <tr> <strong>-j0</strong> .932 <tr> <strong>-j1</strong> .936 <tr> <strong>-j2</strong> .949 <p>These locales determine which bytes are the initial bytes of a multibyte sequence, and control how strings are converted to Unicode strings. If those locales are not supported by the operating system installed on your machine, or the DOS native version of the compiler is running, the lead byte of a multibyte character sequence is: </p> <table class="structure"> <tr><th>switch <th>language <th>prefix bytes <tr><td><strong>-j0</strong> <td>Japanese <td>0x81..0x9F and 0xE0..0xFC <tr><td><strong>-j1</strong> <td>Taiwanese and Chinese <td>0x81..0xFC <tr><td><strong>-j2</strong> <td>Korean <td>0x81..0xFD </table> <p>and the conversion to Unicode is done simply by 0 extending a regular character and stuffing a multibyte sequence into 16 bits. </p> <p>The <strong>-j</strong> switch is obsolete. The <a href="/index.cgi/speech/https://digitalmars.com/ctg/pragmas.html#setlocale">#pragma setlocale()</a> directive is a superior solution.</p> </dd> <dt><a name="dashCapJb"><strong>-Jb</strong> disable empty base class optimization</a> </dt> <dd><p>The "empty base class optimization" causes base classes with no members to add no size to the derived class. Compilers 8.27 and earlier would add 1 to 4 bytes of size per empty base class (depending on alignment). Eliminating this can result in significant performance gains with STL. </p> <p>For link compatibility with code compiled with compilers 8.27 and earlier that used empty base classes, the <strong>-Jb</strong> flag will help. Alternatively, add a <tt>char reserved;</tt> data member to the empty base class definition, which will cause it to have the same storage layout as earlier compilers.</p> </dd> <dt><a name="dashCapJm"><strong>-Jm</strong> relaxed type checking</a> </dt> <dt><strong>-Jm-</strong> strict type checking (default)</dt> <dd><p>Use for legacy C code which relied on the loose type checking of older C compilers. Do not use <strong>-Jm</strong> for new code development. </p> <p><strong>-Jm</strong> is ignored for C++ compilations, since C++ is heavily dependent on strong type checking.</p> </dd> <dt><a name="dashCapJu"><strong>-Ju</strong> char and unsigned char are the same type (unsigned char)</a> </dt> <dt><strong>-Ju-</strong> (default) char and unsigned char are different types</dt> <dd><p>This is useful in compiling some old legacy C code where the author arbitrarilly mixed up using char and unsigned char types. It is equivalent to:</p> <pre>#define char unsigned char </pre> <p><strong>-Ju</strong> does not affect the behavior of runtime library functions like <strong>strcmp()</strong>, which always behave as if chars are signed. </p> <p>Do not use <strong>-Ju</strong> for new code development. </p> <p>Using <strong>-Ju</strong> causes all sorts of problems in C++ code, primarily goofing up overloading based on char types. Using <strong>-Ju</strong> for C++ is not recommended.</p> </dd> <dt><a name="dashCapJ"><strong>-J</strong> char promotions are unsigned</a> </dt> <dt><strong>-J-</strong> char promotions are signed (default)</dt> <dd><p>This affects whether objects of type char are sign-extended or zero- extended when being promoted from char to a larger type. It does not affect the signed char or unsigned char types. char is still a type distinct from unsigned char and signed char. </p> <p>If code is sensitive to <strong>-J</strong> or <strong>-J-</strong>, then it is non-portable, and should be carefully checked to replace the sensitive types with signed char or unsigned char as needed. For instance: </p> <pre>char c; int i = c; </pre> <p>Should be replace with (if it matters):</p> <pre>signed char c; int i = c; </pre> <p>or:</p> <pre>unsigned char c; int i = c; </pre> <p>or:</p> <pre>char c; int i = (signed char) c; int i = (unsigned char) c; int i = c & 0xFF; </pre> <p><strong>-J</strong> does not affect the behavior of runtime library functions like <strong>strcmp()</strong>, which always behave as if chars are signed. </p> <p><strong>-J</strong> causes the macro</p> <pre>#define _CHAR_UNSIGNED 1 </pre> <p>to be defined.</p> </dd> <dt><a name="dashl"><strong>-l</strong>[<em>listfile</em>] Generate source listing file</a> </dt> <dd><p>Generates a source listing file with the name <em>listfile</em>. <em>listfile</em> defaults to being the name of the input file with the extension <strong>.lst</strong> added. To show the effects of the preprocessor in this file, specify the <a href="#dashe">-e</a> option also. The compiler then inserts error messages and line numbers into the listing file. </p> <p>There is no space between <strong>-l</strong> and <em>listfile</em>.</p> </dd> <dt><a name="dashCapL"><strong>-L</strong> Using non-Digital Mars linker</a> </dt> <dd>Digital Mars <a href="/index.cgi/speech/https://digitalmars.com/ctg/optlink.html">linker</a> has some extra features in them (like support for long command lines), <strong>-L</strong> means a non-Digital Mars linker will be run so those features cannot be used. </dd> <dt><a name="dashCapLlinker"><strong>-L</strong><em>linker</em> Use linker <em>linker</em> instead of default.</a> </dt> <dd><p>This is useful if a special linker is being used, or if the linker is not on the <strong>PATH</strong> or in the directory where <strong>dmc</strong> resides. </p> <p>For example, <tt>-L\path\mylink</tt> tells the compiler to run the MYLINK linker in the <tt>\path</tt> directory.</p> </dd> <dt><a name="dashCapLslash"><strong>-L/</strong><em>switch</em> Pass <strong>/</strong><em>switch</em> to linker.</a> </dt> <dd><p>For example, this command:</p> <pre>dmc test -L/packcode -L\test\prog </pre> <p>adds the option /packcode and the library search path <tt>\test\prog</tt> to the linker's command line. </p> </dd> <dt><a name="dashCapM"><strong>-M</strong><em>asm</em> specify assembler to use</a> </dt> <dd><p><strong>MASM</strong> is normally the assembler called by <strong>dmc</strong> when an assembler source file needs to be assembled. Use <strong>-M</strong> to specify an alternate assembler <em>asm</em>. </p> <p>For example, <tt>-M\path\masm</tt> tells the compiler to run the <strong>MASM</strong> in the <tt>\path</tt> directory. </p> </dd> <dt><a name="dashCapMslash"><strong>-M/</strong><em>switch</em> Pass <strong>/</strong><em>switch</em> to assembler</a> </dt> <dt><a name="switch_mn"><strong>-m[tsmclvfnrpxz][do][w][u]</strong> Select memory model</a> </dt> <dd> 16 Bit Models <tr> <strong>t</strong> Tiny: small model program linked specially to create .COM file <tr> <strong>s</strong> Small: small code and data (default) <tr> <strong>m</strong> Medium: large code, small data <tr> <strong>c</strong> Compact:small code, large data <tr> <strong>l</strong> Large: large code and data <tr> <strong>v</strong> VCM (Virtual Code Manager) (obsolete) <tr> <strong>r</strong> Rational Systems 16 bit DOS Extender <tr> <strong>z</strong> Zortech ZPM 16 bit DOS Extender (obsolete) 32 Bit Models <tr> <strong>f</strong> OS/2 2.0 32 bit flat model (not supported) <tr> <strong>n</strong> Win32 32 bit flat model (default) <tr> <strong>p</strong> Pharlap 32 bit DOS Extender (obsolete) <tr> <strong>x</strong> DOSX 32 bit DOS Extender (obsolete) <p>Memory Model Modifiers</p> <dl> <dt><strong>d</strong> DOS 16 bit (default)</dt> <dt><strong>o</strong> OS2 16 bit (obsolete)</dt> <dd>Indicates code will be targeted towards an OS/2 16 bit executable.</dd> <dt><strong>w</strong> assume SS != DS</dt> <dd>Use the w flag in combination with the -m option to make sure that the stack segment (SS) is not equal to the data segment (DS). Certain types of executables require that the DS and the SS be different. These are: <ul> <li> 16-bit dynamic link libraries (DLLs) <li> 16-bit multithreaded code </ul> </dd> <dt><strong>u</strong> reload DS</dt> <dd><p>Use the u flag in combination with the -m option to instruct the compiler to always reload DS from the current value of DGROUP upon function entry. Note that u does not also imply that the DS and the SS are different (use w for that, as described above). </p> <p>For 16 bit Windows code, use the -W switches instead of the w or u modifiers to the -m flag. This will prevent order dependencies, since a -W switch appearing after a -m switch will override the w or u modifiers on the -m switch, and vice versa. </p> </dd> </dl> </dd> <dt><a name="dashCapNc"><strong>-Nc</strong> function level linking</a> </dt> <dd>This causes each global or static function to be placed into its own COMDAT record. This will enable function level linking. Function level linking means that only functions actually referenced by other code will be pulled in and placed in the final executable.</dd> <dt><a name="dashCapNCapC"><strong>-NC</strong> don't generate COMDATs (obsolete)</a> </dt> <dd>Avoid using this switch. It is now obsolete, since current linkers now all support COMDAT records.</dd> <dt><a name="dashCapNCapD"><strong>-ND</strong> compile and link with DLL version of runtime library</a> </dt> <dd>Defines and sets _MT and _DLL to one. Changes the embedded RTL name from SNN.LIB to SND.LIB. This must be used only with the Win32 memory model (-mn). The DLL version of the runtime library is <tt>\dm\bin\sccrt70.dll</tt>.</dd> <dt><a name="dashCapNCapF"><strong>-NF</strong> ignore extended keywords</a> </dt> <dd>The keywords __far, __huge, __loadds, __interrupt, __handle are ignored. (This is the default for N and F memory models.) -NF can be useful for compiling old 16 bit code for the x or p memory models.</dd> <dt><a name="dashCapNCapL"><strong>-NL</strong> Do not embed default library record</a> </dt> <dd>The compiler normally embeds in the object file a record indicating the default runtime library to be linked in. -NL suppresses this embedding. This is useful when: <ul> <li> Compiling code that will go into a library, getting rid of all those records can result in a substantial reduction in library size. <li> Compiling code that will be linked with code generated by other compilers. </ul> </dd> <dt>dashCapNCapLlibfile, <strong>-NL</strong><em>libfile</em></dt> <dd>Embed the filename <em>libfile</em><strong>.lib</strong> into the object file instead of the default.</dd> <dt><a name="dashCapNs"><strong>-Ns</strong> place expression strings in code seg</a> </dt> <dd><p>Places strings that appear in expressions into the code segment rather than the data segment. Expression strings are always placed anyway in the code segment if the type of the expression is __cs*. The <strong>-Ns</strong> switch will place expression strings into the code segment that are typed as far pointers (the default in large data models). </p> <p><strong>-Ns</strong> is ignored for FLAT memory models (<strong>-mn</strong>, <strong>-mf</strong>). </p> <p><strong>-Ns</strong> is useful for 16 bit Windows programs to reduce DGROUP usage. Note that strings placed in the code segment cannot be written to. To write into a string and use <strong>-Ns</strong>, make the particular writable string a static array. </p> <p><strong>-Ns</strong> does not place strings in statically initialized data structures into the code segment.</p> </dd> <dt><a name="dashCapNCapS"><strong>-NS</strong> new code seg for each function</a> </dt> <dd><p>Causes a new code segment to be started each time a global far function is encountered. The name of the segment is the name of the function, with _TEXT appended. </p> <p>Because near functions cannot cross segment boundaries, all near functions must immediately follow any global functions that call them and cannot be called by more than one global function.</p> </dd> <dt><a name="dashCapNt"><strong>-Nt</strong> use old template name mangling scheme (obsolete)</a> </dt> <dd>By default, the compiler generates VC compatible name mangling. For compatibility with object code with pre-version 7.2 compilers, the -Nt switch enables the old template mangling scheme. </dd> <dt><a name="dashCapNCapT"><strong>-NT</strong><em>name</em> Set code segment name to <em>name</em>.</a> </dt> <dd>Sets code segment name, rather than using the default, <em>module</em><strong>_TEXT</strong>. </dd> <dt><a name="dashCapNCapV"><strong>-NV</strong> Put virtual function tables in far data segments.</a> </dt> <dd><p>Put virtual function tables in far data segments. by default. The default behavior is to put vtbls in the code segment for the Compact and Large memory models and for all 32-bit data models. For programs compiled with the Tiny, Small, or Medium models, the compiler places vtbls in DGROUP. </p> <p>This option is useful for saving code space in Compact and Large model programs. </p> <p>Borland C++ puts vtbls in the data segment by default; Microsoft C++ treats them as does Digital Mars C++.</p> </dd> <dt><a name="dasho"><strong>-o</strong>[<strong>-+</strong><em>flag</em>] run optimizer with <em>flag</em></a> </dt> <dd> <tr> <strong>-o-</strong> No optimization (default) <tr> <strong>-o</strong> Optimize for program speed <tr> <strong>-o+space</strong> Optimize for program size </dd> <dt><a name="dashoSPP"><strong>-o</strong> SPP only: send result to stdout</a> </dt> <dt><a name="dashofilename"><strong>-o</strong><em>filename</em> Specify output <em>filename</em></a> </dt> <dd>This specifies the name of the object [<strong>.obj</strong>] file if the -c switch is used, otherwise it specifies the output executable [<strong>.exe</strong>] file name. The dot extension is optional. </dd> <dt><a name="dashp"><strong>-p</strong> turn off autoprototyping</a> </dt> <dt><strong>-p-</strong> turn on autoprototyping (default)</dt> <dd><p>Autoprototyping is a Digital Mars C feature where if a function call is made and there is no prototype for the function, the compiler will create a prototype for that function based on the number and types of the arguments to it. Subsequent calls to that function will be checked against that prototype. </p> <p>This obviously can cause trouble if functions that accept a variable number of arguments (like printf()) are called without a prototype for that function in scope. </p> <p>Autoprototyping is irrelevant in C++ or if <strong>-r</strong> is used, because prototypes are then required.</p> </dd> <dt><a name="dashCapP"><strong>-P</strong> Default to pascal linkage</a> </dt> <dd><p>Makes Pascal the default linkage for all functions and global data, instead of cdecl. Since all C library routines have cdecl linkage, they must be prototyped as such before being called. The main function must also be declared to have cdecl linkage or the linker cannot find it. For more information on declaring code to have alternative linkage, see <a href="/index.cgi/speech/https://digitalmars.com/ctg/ctgMixingLanguages.html">Mixing Languages</a>. </p> <p>Using Pascal as the default linkage type results in about a 3% code size reduction and corresponding speed increase in generated code.</p> </dd> <dt><a name="dashCapPdash"><strong>-P-</strong> Default to cdecl linkage</a> </dt> <dt><a name="dashCapPz"><strong>-Pz</strong> Default to stdcall linkage</a> </dt> <dt><a name="dashr"><strong>-r</strong> strict prototyping</a> </dt> <dt><strong>-r-</strong> turn off <strong>-r</strong> (default)</dt> <dd>Enforces strict prototyping (all functions must be declared and prototyped before use). Standard library functions must include the appropriate header files. This behavior is the default for the C++ compiler and is highly recommended for C code, since it helps eliminate errors caused by type mismatches.</dd> <dt><a name="dashCapR"><strong>-R</strong> put switch tables in code segment</a> </dt> <dd><p>Switch tables are normally placed in the data segment (DGROUP). Sometimes, DGROUP space can be very limited, so the <strong>-R</strong> switch can be used to place switch tables into the code segment. Generated code will be slightly bigger and slower for switch statements with <strong>-R</strong>. </p> <p><strong>-R</strong> is ignored for 32 bit programs.</p> </dd> <dt><a name="dashs"><strong>-s</strong> stack overflow checking</a> </dt> <dd><p>Inserts code into the function prologs to check for stack overflows. The resulting program generates an error message and aborts if it detects a stack overflow at run-time. This option is particularly useful for code with heavily recursive functions. </p> <p>This switch is of interest mainly for 16 bit programs. </p> <p>Note: The compiler does not support stack overflow checking for programs compiled with the DOSX (-mx) memory model.</p> </dd> <dt><a name="dashCapS"><strong>-S</strong> always generate stack frame</a> </dt> <dd><p>Generates a stack frame for each function. -S is typically used when working with a symbolic debugger, but it can be specified by itself. The compiler always generates stack frames with either the -g or -gs option. </p> <p>Without -S, the compiler does not generate a stack frame for functions with no local variables and no arguments.</p> </dd> <dt><a name="dashu"><strong>-u</strong> suppress predefined macros</a> </dt> <dt><a name="dashv"><strong>-v[0|1|2]</strong> verbose compile</a> </dt> <dd> <p><strong>-v0</strong> Do not display any messages.</p> <p><strong>-v1</strong> Default</p> <p><strong>-v</strong><br></p> <p><strong>-v2</strong> Displays source and header file names, classes, and functions while they are being compiled. Displays total compilation time.</p> </dd> <dt><a name="dashw"><strong>-w[-|n|x]</strong></a> warning messages</dt> <dd> <dl> <dt><strong>-w</strong> suppress all warning messages</dt> <dt><strong>-w</strong><em>n</em> suppress warning message <em>n</em></dt> <dd>See <a href="/index.cgi/speech/https://digitalmars.com/ctg/warnings.html">Warnings and associated warning numbers</a> for messages.</dd> <dt><strong>-w-</strong> enable all warning messages (default)</dt> <dt><a name="dashwc"><strong>-wc</strong></a> warn on C style casts</dt> <dd>This makes it easy to find and upgrade all the C style casts in C++ code to C++ style casts.</dd> <dt><a name="dashwx"><strong>-wx</strong></a> treat warnings as errors</dt> <dd>Warning messages tend to quickly scroll off the screen and go unnoticed, especially during building projects with lots of source files. <strong>-wx</strong> will treat warnings as errors, so they cannot be accidentally overlooked.</dd> </dl> </dd> <dt><a name="dashCapW"><strong>-W</strong>{<strong>0123ADadefmrstuvwx-+</strong>}</a> Windows prolog/epilog</dt> <dd><strong>1</strong>: Full <strong>2</strong>: Reduced <strong>3</strong>: Smart callback <strong>A</strong>: EXE <strong>D</strong>: DLL <br> See <a href="/index.cgi/speech/https://digitalmars.com/ctg/windowspe.html">Windows Prolog/Epilog Code Generation</a>. </dd> <dt><a name="dashx"><strong>-x</strong></a> turn off compilation error maximum</dt> <dd>Since many reported errors in a source file tend to be cascaded from the first error, the compiler normally aborts compiling a file after a certain number of errors are reported. Using <strong>-x</strong> will cause the compiler to proceed and try to compile the rest of the file.</dd> <dt><a name="dashCapXCapD"><strong>-XD</strong></a> instantiate template for any functions declared but not defined</dt> <dt><strong>-XD-</strong> turn off <strong>-XD</strong> (default)</dt> <dd><p>Consider the following:</p> <pre>template<T> int func(T) { return T; } int func(double); </pre> <p>By default, since the specific declaration of func(double) exists, the compiler will not generate an instance of the template func(double), even if func(double) is called later in the source file. The programmer must provide an explicit definition of func(double) with a body at some point in the source code to the program. </p> <p>If <strong>-XD</strong> is specified, the two lines above tell the compiler to generate an instance of func(double) from the template of func(T) as long as no explicit function body for func(double) appears in that same source file. </p> <p>With <strong>-XD</strong>, the generated instance is placed into a COMDAT record, which means that if an explicit body is provided in another source file, that explicit definition will override the generated COMDAT definition. If the source file with the explicit body is compiled with <strong>-Nc</strong> (generate COMDATs for functions), then a linker error will result because there will be two different definitions for func(double). </p> <p><strong>-XD</strong> is the way the Digital Mars compiler versions previous to 7.0 worked by default, and is so provided for compatibility with previous versions. </p> </dd> <dt><a name="dashCapXCapI"><strong>-XI</strong><em>spec</em> Create instance of template</a> </dt> <dd><p>Generate specific instances of templates that appear in the source file being compiled. For example, suppose the file test1.cpp contains the function template:</p> <pre>template<class T> T min(T a, T b) { return a < b ? a : b; } </pre> <p>To create two instances of min() from test1.cpp (one for integers and one for doubles), use this command line:</p> <pre>dmc -c -XImin(int, int) -XImin(double, double) test1 </pre> <p>Similarly, suppose stack.h contains this class template:</p> <pre>template<class T> class stack { private: T* top; T* bottom; int size; public: stack(int s) { top = bottom = new T[size = s]; } ~stack() { delete[size] bottom; } void push(T a) { *top++ = a; } T pop() { return *--top; } int size() const; } </pre> <p>and test2.cpp contains this template:</p> <pre>#include <stack.h> template<class T> int stack<T>::size() const { return top - bottom; } </pre> <p>To create a class for a stack of float types, use this command line:</p> <pre>dmc -c "-XIstack<float>" test2 </pre> <p>Enclose this instance of the -XI option in quotation marks, since it contains the characters < and >. Without the quotation marks, the operating system would interpret the less-than (<) and greater-than (>) signs as file-redirection commands.</p> </dd> <dt><a name="dashCapXCapN"><strong>-XN</strong> no template function instantiation</a> </dt> <dd>Do not automatically expand any template function bodies.</dd> <dt><strong>=</strong><em>nnnn</em> set stack size for compiler passes (obsolete)</dt> <dt><a name="dash023456"><strong>-[0|2|3|4|5|6]</strong> 88/286/386/486/P5/Pro code</a> </dt> <dd><p>Select CPU instruction type.</p> <tr> <strong>-0</strong> Generate code for 8088 and later CPUs <tr> <strong>-2</strong> Generate code for 286 and later CPUs <tr> <strong>-3</strong> Generate code for 386, 486, Pentium and Pentium Pro, and select instruction sequences that favor the 386 <tr> <strong>-4</strong> Generate code for 386, 486, Pentium and Pentium Pro, and select instruction sequences that favor the 486 <tr> <strong>-5</strong> Generate code for 386, 486, Pentium and Pentium Pro, and select instruction sequences that favor the Pentium <tr> <strong>-6</strong> Generate code for 386, 486, Pentium and Pentium Pro, and select instruction sequences that favor the Pentium Pro <p>This chart shows which CPUs each switch is compatible with:</p> <table class="structure"> <tr><th> CPU <th>-0 <th>-2 <th>-3 <th>-4 <th>-5 <th>-6 <tr><td>8088 <td>Y <td>N <td>N <td>N <td>N <td>N <tr><td>286 <td>Y <td>Y <td>N <td>N <td>N <td>N <tr><td>386 <td>Y <td>Y <td>Y <td>Y <td>Y <td>Y <tr><td>486 <td>Y <td>Y <td>Y <td>Y <td>Y <td>Y <tr><td>Pentium <td>Y <td>Y <td>Y <td>Y <td>Y <td>Y <tr><td>Pro <td>Y <td>Y <td>Y <td>Y <td>Y <td>Y </table> <p>Selecting a CPU type does not affect the memory model chosen, but <strong>-0</strong> and <strong>-2</strong> are invalid for 32 bit memory models. Since running Windows programs on an 8088 or a 286 is completely impractical, use <strong>-3</strong>, <strong>-4</strong> or <strong>-5</strong> even when generating 16 bit Windows code. </p> <p><strong>-6</strong> is the default for 32 bit memory models.</p> <p>The compiler supports the MMX instruction set in the inline assembler. MMX support is not affected by the CPU instruction type selection. </p> <p>When using <strong>-3</strong> or higher for 16 bit programs, beware of crash bugs resulting from conflicts with DOS terminate-and-stay-resident programs (TSRs) that do not save or restore the high-order 16 bits of the 32-bit registers. </p> </dd> </dl> </div> <div id="footernav"> <a href="https://www.digitalmars.com/" title="digitalmars.com">Home</a> | <a href="/index.cgi/speech/https://digitalmars.com/ctg/../rtl/rtl.html" title="Runtime Library Reference">Runtime Library</a> | <a href="/index.cgi/speech/https://digitalmars.com/ctg/../ugr/ugr.html" title="IDDE Reference">IDDE Reference</a> | <a href="/index.cgi/speech/https://digitalmars.com/ctg/../stl/index.html" title="Standard Template Library">STL</a> | <a href="https://www.digitalmars.com/advancedsearch.html" title="Search Digital Mars web site">Search</a> | <a href="https://www.digitalmars.com//download/freecompiler.html" title="download C++">Download</a> | <a href="https://www.digitalmars.com/NewsGroup.html" title="Forums">Forums</a> </div> <div id="copyright"> Copyright © 1999-2022 by Digital Mars ®, All Rights Reserved | Page generated by <a href="https://dlang.org/spec/ddoc.html">Ddoc</a>. </div> </div><div class="naked_ctrl"> <form action="/index.cgi/speech" method="get" name="gate"> <p><a href="http://altstyle.alfasado.net">AltStyle</a> によって変換されたページ <a href="https://digitalmars.com/ctg/sc.html">(->オリジナル)</a> / <label>アドレス: <input type="text" name="naked_post_url" value="https://digitalmars.com/ctg/sc.html" size="22" /></label> <label>モード: <select name="naked_post_mode"> <option value="default">デフォルト</option> <option value="speech" selected="selected">音声ブラウザ</option> <option value="ruby">ルビ付き</option> <option value="contrast">配色反転</option> <option value="larger-text">文字拡大</option> <option value="mobile">モバイル</option> </select> <input type="submit" value="表示" /> </p> </form> </div> </body> </html>