The following small changes (apart from those in ChangeLog's) have been made
to PGCC+EMX relatively to GCC+EMX 2.7.2.1 (unordered):

o PGCC has NO bound checking.

o The symbol __OS2__ is defined if -Zomf is used.

o I've removed some of Eberhard Mattes' patches that were related to 8.3
  naming convention. FAT is ugly, besides you mostly won't have any problems
  with 8.3 names even without these patches. They were related mostly to
  GCC-developer related things, like .cse2, .flow, .combine, .sched and
  other file name extensions. If you need these files, you should use
  a normal filesystem :-)

o The -ZC++-comments switch is gone now (hopefully forever) since GCC
  always enable C++-style comments (unless -traditional or -lang-c89 is
  specified)

o The -Zexe switch now works correctly (before it worked only in couple
  with -o switch). ld and emxomfld were patched too for this. Also now
  the -Zexe option not only creates a fresh file without extension
  to keep "make" happy; the behaviour has been changed to copy a file
  called ldstub.bin that should be located in same directory where
  ld or emxomfld is into the file with same name as executable but without
  extension: this avoids two problems at once: first, many "configure"
  scripts expects after compiling a test program to obtain a *non-empty*
  file; and second, they expect the file to be runnable, otherwise C compiler
  is considered a cross-compiler. ldstub determines the name under which
  it has been launched and launches in turn the executable that has same
  name but with ".exe" appended. So, for example, if you copy ldstub.bin
  into "sh" then when you do from, say, bash:

  [c:/] ./sh

  you will launch "sh" which in turn will look for "sh.exe" (located in
  same directory as "sh" itself) and will run it.

o All compilers were compiled with -Zcrtdll, so you will need an
  installed EMX runtime to run them. Anyway, I think everybody reading
  this already have it :-)

o The -mprobe switch is retained for backward compatibility, however it
  is highly recommended that you use -mstack-arg-probe and -mno-stack-arg-probe
  instead since these options are new from mainstream GCC version, and maybe
  someday -mprobe will disappear.
  Another switch that has to do with stack probing is -f{no-}stack-check.
  These switches have same functionality as -m{no-}stack-arg-probe but uses
  inline instructions instead of alloca call, so they're faster. Here is how
  alloca(20000) is compiled with different switches:

  without any switches:

	subl $20000,%esp

  with -mstack-arg-probe:

	movl $20000,%eax
	call __alloca

  with -fstack-check options:

	movl $0,-4392(%esp)
	movl $0,-8488(%esp)
	movl $0,-12584(%esp)
	movl $0,-16680(%esp)
	movl $0,-24392(%esp)
	addl $-20000,%esp

o Now alloca() is stack-probe safe, i.e. if you`re compiling with
  -mstack-arg-probe switch, alloca() will do stack probes.

o 64-bit ([signed & unsigned] long long) division is now FAST! :-) Its written
  in assembly now, and I`ve optimized them by hand.

o -mepilogue did not worked in C++ and possibly other languages which mangles
  names. Fixed.

o _set_new_handler now is called set_new_handler. However, _set_new_handler
  will work too as an alias.

o There is a new optional environment variable: CLH_TERM.
  If GCC was compiled with built-in command-line help system (try gcc --help)
  this variable will be used (or TERM as a fallback) to find the corresponding
  entry in TERMCAP file to highlight command-line help. I've included my
  TERMCAP file in this directory as a example. I'm using 'SET TERM=OS2'.
  If CLH_TERM is equal to '-' (i.e. SET CLH_TERM=-) command-line help will
  not be colored.

o Libgcc has been put in a separate DLL. This happened because libgcc changes
  often - with each new major gcc release, sometimes even in minor releases.
  To avoid conflicts with future/previous libgcc versions, libgcc will have
  a name consisting of 'gcc' and gcc's internal version number without dots.
  For example, gcc version 2.90.27 will have its runtime in gcc29027.dll.

Known bugs and limitations:

o Exceptions in C++ currently are single-threaded. This means you cannot
  throw in two threads at the same time, otherwise you'll crash.

o emxomf now traps (sometimes?) when compiling with -g (debug) switch.

o f77 compiler does not incorporate the changes made for the `main' ported
  version for OS/2. I do not know whenever there are other changes other than
  those needed `just to make it work'.

--------------------------------------------------------------------------------
                             PGCC/2 change history
--------------------------------------------------------------------------------

(*) pgcc-1.1.1
  - Upgraded to pgcc 1.1.1
  - Upgraded to emx 0.9d: PGCC will not work anymore with emx 0.9c.
  - Now command-line help works without termcap; this is better since it
    achieves consistent results across different termcap files (the one that
    comes with emx works not too well with CLH). The CLH_TERM variable
    can be assigned three different values: "-" for non-colored output,
    "mono" for monochrome output and anything other (or unset) for colored
    output.
  - Exceptions will work from now ONLY if you will link with g++ and ONLY
    if you did not used -fno-exceptions during linking. Otherwise a different
    version of libgcc is used that has smaller size overhead (~10K) by the
    cost of exception handling.

(*) pgcc-1.0.2 release 2 - minor bugfixes
  - Re-compiled ld.exe and emxomfld.exe to not use gcc290.dll from pgcc-1.0.0
  - Changed front-end to pre-define __OS2__ symbol when using -Zomf
  - Fixed an inconsistency between ld and emxomfld: ld used ldstub.bin when
    run with -Zexe while emxomfld searched for ldstub.bin. Now the "launcher"
    stub is always called ldstub.bin.
  - minor bug in emxfix.cmd: lib/st and lib/mt already exists, so there is
    no need to create them.
  - New libraries: gpp*.a (which have almost the same functionality as their
    gcc*.a counterparts). I was forced to split g++ runtime from gcc runtime
    since g++ when used with frame-unwind exceptions required a slightly longer
    initialization sequence which pulls a lot of unused code into executables,
    even for plain C and F77 not speaking of C++ code without exceptions.
    So I suggest now linking with gcc even C++ code without exceptions -
    this will produce slightly smaller executables (5-10K).
  - Fixed the bug with creating a ".exe" file when feeding only linker
    files to frontent (ex: gcc -s a.o b.o c.o will produce ".exe").
    Now it takes the basename of first object file and appends .exe or .dll.

(*) pgcc-1.0.2
  - Upgraded to egcs-1.0.2.
  - Ooops! Due to a bug in my makefiles, libgcc previously used C versions
    of some functions instead of optimized versions I wrote in
    config/i386/emx-libgcc1.asm. 64-bit division should be slightly faster
    now.
  - Renamed dynamically-loaded libgcc from gcc290.dll to gcc29027.dll.
    This happened because libgcc in pgcc-1.0.2 has been changed, to
    avoid conflicts with previous versions of gcc*.dll.
  - Added include/cpp/new, include/cpp/exception, include/cpp/typeinfo files.
    I don't really know what they are for :-) I don't use libstdc++.
  - Included GNU -liberty library into base PGCC/2 binary distribution.
    The files added were:
     - libiberty.h - mostly interface for string functions in libiberty
     - objalloc.h  - obstack management
     - obstack.h   - same
     - getopt.h    - GNU getopt (getopt_long included too).
                     Replaces EMX's getopt.h
     - demangle.h  - C++/Java name demangling functions
     - fnmatch.h   - Wildcard filename match function
                     Replaces EMX's fnmatch.h
     - ansidecl.h  - auxiliary file
     - iberty.a    - static library
     - ibertydll.a - import library
     - iberty.dll  - dynamic library

    To link against static version of GNU -liberty library use:

     gcc [...] -liberty

    To link against dynamic version of GNU -liberty library use:

     gcc [...] -libertydll

    iberty.dll should be on your LIBPATH (and distributed with your
    programs, if used). Distribution policy is contained in file COPYING.

(*) pgcc-1.0 release 2
  - multi-threaded and single-threaded libstdc++ library!
  - fixed a bug with _IO_flockfile and _IO_funlockfile in libstdc++
  - fixed a number of minor bugs in supplied header files
    - removed limits.h - emx's is good enough
    - removed float.h - emx's is good enough
    - removed sysinclude.h which is garbage
    - removed proto.h which is garbage
    - fixed a definition conflict with emx headers in
      varargs.h and stdarg.h
  - changed behaviour of command-line help. Now by default "gcc -h"
    will list a digest of most used GCC options. To see the full help
    index use gcc -h* or gcc --help=*

(*) pgcc-1.0 release 1
  This was the first release of pgcc-1.0 for OS/2
