From: Jeffrey A Law <law@cygnus.com>
To: egcs-announce@cygnus.com, gnu-gcc-announce@prep.ai.mit.edu,
compilers@iecc.com
Cc: egcs@cygnus.com, gcc2@cygnus.com
Subject: egcs-1.0.1 release
Date: Thu, 04 Dec 1997 14:03:00 -0000 [thread overview]
Message-ID: <19161.884115021@hurl.cygnus.com> (raw)
January 6, 1998
We are pleased to announce the release of egcs-1.0.1.
egcs is a collaborative effort involving several groups of hackers using an
open development model to accelerate development and testing of GNU compilers
and runtime libraries.
egcs-1.0.1 is a minor update to the egcs-1.0 compiler to fix a few critical
bugs and add support for Red Hat 5.0 Linux. Changes since the egcs-1.0
release:
* Add support for Red Hat 5.0 Linux and better support for Linux
systems using glibc2.
* Compatability with both egcs-1.0 and gcc-2.8 libgcc exception handling
interfaces (see below for further discussion).
* Various bugfixes in the x86, hppa, mips, and rs6000/ppc backends.
* A few machine independent bugfixes, mostly to fix code generation bugs
when building Linux kernels or glibc.
* Fix a few critical exception handling and template bugs in the C++
compiler.
* Fix Fortran namelist bug on alphas.
* Fix build problems on x86-solaris systems.
To avoid future compatibility problems, we strongly urge anyone who is planning
on distributing shared libraries that contain C++ code to upgrade to egcs-1.0.1
first (see http://www.cygnus.com/egcs/egcs-1.0.1.html for details about the
compatability issues as well as additional information about the bugfixes since
the egcs-1.0 release).
egcs contains many improvements and features not found in gcc-2.7 and
even the soon to be released gcc-2.8 compilers.
* Integrated C++ runtime libraries, including support for most major
linux systems!
* The integrated libstdc++ library includes a verbatim copy of
SGI's STL release.
* Integrated GNU Fortran compiler
* New instruction scheduler
* New alias analysis code
See the egcs web page for a more complete list of new features, installation
instructions, build/test status, caveats, mailing lists, etc.
http://www.cygnus.com/egcs
You can ftp egcs-1.0.1 either as a full release, or as diffs from the egcs-1.0
release from the following sites:
Master site:
US (California) ftp.cygnus.com:/pub/egcs
Alternate site:
US (Massachusetts) cambridge.cygnus.com:/pub/egcs
Direct Mirrors:
US (east coast) ftp.goof.com:/pub/pcg/egcs
US (Arizona) ftp.ninemoons.com:/pub/egcs
US (California) ftp.yggdrasil.com:/mirrors/site/ftp.cygnus.com/pub/egcs
UK sunsite.doc.ic.ac.uk:/packages/gnu/cygnus/egcs
Austria gd.tuwien.ac.at:/gnu/egcs
France ftp.ilog.fr:/pub/Mirrors/egcs
France ftp.lip6.fr:/pub/egcs
Czech Republic sunsite.mff.cuni.cz:/GNU/cygnus/egcs
Denmark sunsite.auc.dk:/pub/egcs
Germany (Berlin) ftp.fu-berlin.de:/unix/languages/egcs
Germany ftp.gwdg.de:/pub/cygnus/egcs
Poland (Warsaw) sunsite.icm.edu.pl:/pub/programming/egcs
Sweden ftp.sunet.se:/pub/gnu/egcs
Sites which mirror indirectly via ftp.goof.com:
Japan ftp.u-aizu.ac.jp:/pub/lang/C/pcg/egcs
France ftp.maisel.int-evry.fr:/pub/linux/pentium/egcs
reply other threads:[~1997-12-04 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19161.884115021@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=compilers@iecc.com \
--cc=egcs-announce@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=gnu-gcc-announce@prep.ai.mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).