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

This option is identical to the "zm" option (see zm) except for the
following large code model consideration.
Instead of placing each function in a segment with a different name, the
code generator will place each function in a segment with the same name (the
name of the module suffixed by "_TEXT").

The advantages to this option are:

 1. All functions in a module will reside in the same physical segment in an
    executable.

 2. The "near call" optimization for static functions in large code models
    is not disabled (e.g., the function foo in the example above will be
    "near called".  Static functions will always be "near called" in large
    code models.

 3. The problem associated with calling "near" functions goes away since all
    functions in a module will reside in the same physical segment (e.g.,
    the function foo1 is "near" in the example above).

The disadvantages to this option are:

 1. The size of a physical segment is restricted to 64K in 16-bit
    applications.  Although this may limit the number of functions that can
    be placed in the segment, the restriction is only on a "per module"
    basis.

 2. Although less constricting, the size of a physical segment is restricted
    to 4G in a 32-bit application.