Click above to get retro games delivered to your door ever month!

The generated code is placed in the group called "<codegroup>".  The default
"text" segment name will be "<codegroup>_TEXT" but this can be overridden by
the "nt" option.
Example:

     C>compiler_name report /g=RPTGROUP /s

(16-bit only) <<

This is useful when compiling applications for small code models where the
total application will contain more than 64 kilobytes of code.  Each group
can contain up to 64 kilobytes of code.  The application follows a "mixed"
code model since it contains a mix of small and large code (intra-segment
and inter-segment calls).  Memory models are described in the chapter
entitled 16-bit Memory Models.  The far keyword is used to describe routines
that are referenced from one group/segment but are defined in another
group/segment.

For small code models, the "s" option should be used in conjunction with the
"g" option to prevent the generation of calls to the C run-time "stack
overflow check" routine ( __STK ).  You must also avoid calls to other
"small code" C run-time library routines since inter-segment "near" calls to
C library routines are not possible.

>> (16-bit only)