Message-Id: <200212021714.gB2HEhc11158@delorie.com> From: Andris Pavenis To: djgpp-announce AT delorie DOT com Subject: ANNOUNCE: DJGPP port of GCC-3.2.1 Date: Mon, 2 Dec 2002 18:15:36 +0200 User-Agent: KMail/1.5 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Reply-To: djgpp AT delorie DOT com This is an announcement of DJGPP port of gcc-3.2.1 GCC used to stand for the GNU C Compiler, but since the compiler supports several other languages aside from C, it now stands for the GNU Compiler Collection. See http://gcc.gnu.org/gcc-3.2/changes.html for more detailed information about new features and other changes in gcc-3.2.1 See http://gcc.gnu.org/ml/gcc/2002-11/msg00445.html for GCC-3.2.1 release notes and list of fixed bugs. Currently C, C++, Fortran and Objective C compilers are supported for DJGPP. Java compiler is not ported and are not included. ADA compiler (as it itself is written in ADA) is able to bootstrap itself, but this is practically only test I have done. ===================================================================== NOTE: I have changed to use DWARF2 debugging info by default (when You specify GCC command line option -g or -g3, ...). DWARF2 debugging info was already available for DJGPP since GCC-3.0, but was not the default. As result You need also new version of GDB for debugging: gdb521b.zip (or newer when available) from DJGPP distribution or recent build of RHIDE from http://rhide.sorceforge.net/snapshots. One can still use COFF (GCC command line option -gcoff) and stabs (command line options -gstabs, -gstabs+) for debugging. Also symify.exe from djdev203.zip works with COFF debugging info only. You need bfdsymify.exe instead (from gdb521b.zip) when DWARF2 or stabs debuging info is being used ===================================================================== NOTE: You need last update of djdev203.zip with timestamp of August 2002 or later. ===================================================================== Archives are available from DJGPP distribution in Simtelnet (and mirror sites) in directory v2gnu: There are 6 archives: gcc321.README - readme file from DJGPP port of GCC-3.2.1. It's in separate file to avoid need to download large archives to get this file. gcc321s.zip - sources of gcc-3.2.1. I put all sources in a single archive. This file is only needed if You're want to rebuild gcc-3.2.1 from sources. gcc321b.zip - binaries of C compiler gpp321b.zip - binaries of C++ compiler (needs gcc321b.zip) g77321b.zip - binaries of Fortran compiler (needs gcc321b.zip) objc321b.zip - binaries of Objective C compiler (needs gcc321b.zip) gcc321s2.zip - shell script and patches for original gcc-3.2.1. I used them to generate gcc-3.2.1 sources for DJGPP (gcc321s.zip). ada321b.zip - binaries of ADA compiler (warning: practically untested) Files user need: Programming languages Needed files C gcc321b.zip C++ gcc321b.zip, gpp321b.zip Fortran gcc321b.zip, g77321b.zip Objective-C gcc321b.zip, objc321b.zip ADA ada321b.zip, gcc321b.zip NOTE: gcc32b.zip contains file cxxfilt.exe and there is file with same name in binutils (for example bnu213b.zip). You can safely overwrite the old one. For more information about this port see archive gnu/gcc-3.21/readme.DJGPP after unpacking either gcc321b.zip or gcc321s.zip or get file gcc321.README from directory v2gnu in DJGPP distribution Also please DON'T mix C++ libraries (or object files) built with different compiler versions. C++ sources should be recompiled (seems that there is no need to do this for C sources). Object files generated by GCC-3.2.1 from C++ sources are incompatible with object files (or libraries) generated from C++ sources by any earlier GCC version. So all C++ sources must be recompiled after upgrade to GCC-3.2.1. System requirements =================== Latest update of DJGPP-2.03 (or above when available). Please verify whether You have a newest one. binutils-2.13 or above. It's no more possible to use binutils-2.8.1 or 2.9.1. Command line option -mno-bnu210 is no more supported. Perhaps binutils-2.11.2 or 2.12 could also be used but are not tested Some warning for users of C++. C++ compiler in gcc-3.2.1 does more strict syntax checking than gcc and egcs versions older than gcc-3.1. As result errors are generated in many places where earlier one got warnings. Note for users of C++ IO classes fstream, ifstream, ofstream ============================================================ There is a regression against GCC versions 2.95.3 and earlier: Member functions tellp(), tellg(), seekp() and seekg() are broken when stream is opened not in binary mode. If You are going to use any similar functions You should open stream in binary mode. Don't ask me when it will be fixed as I don't know that. I'm also not sure I'll spend much time trying to fix that. Send suggestions and bug reports concerning the DJGPP port of GCC to comp.os.msdos.djgpp or . Happy hacking Andris Pavenis