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.3 Release
Date: Thu, 04 Dec 1997 14:03:00 -0000 [thread overview]
Message-ID: <9751.895392373@hurl.cygnus.com> (raw)
egcs-1.0.3
May 15, 1998
We are pleased to announce the release of egcs-1.0.3.
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.3 is a minor update to the egcs-1.0.2 compiler to fix a few
problems reported by Red Hat for builds of Red Hat 5.1.
* Generic bugfixes:
+ Fix a typo in the libio library which resulted in incorrect
behavior of istream::get.
+ Fix the Fortran negative array index problem.
+ Fix a major problem with the ObjC runtime thread support
exposed by glibc2.
+ Reduce memory consumption of the Haifa scheduler.
* Target specific bugfixes:
+ Fix one x86 floating point code generation bug exposed by
glibc2 builds.
+ Fix one x86 internal compiler error exposed by glibc2 builds.
+ Fix profiling bugs on the Alpha.
+ Fix ImageMagick & emacs 20.2 build problems on the Alpha.
+ Fix rs6000/ppc bug when converting values from integer types
to floating point types.
An important goal of egcs is to allow wide scale testing of new
features and optimizations which are still under development. However,
egcs has been carefully tested and should be comparable in quality to
most gcc releases.
egcs-1.0.3 is based on an August 2, 1997 snapshot of the gcc-2.8
development sources; it contains nearly all of the new features found
in gcc-2.8.
egcs also contains many improvements and features not found in gcc-2.7
or gcc-2.8.
* Integrated C++ runtime libraries, including support for most major
GNU/Linux systems!
* The integrated libstdc++ library includes a verbatim copy of
SGI's STL release instead of a modified copy.
* Integrated GNU Fortran compiler
* New instruction scheduler
* New alias analysis code
See the egcs web page for a more complete list of new features
found in egcs-1.0.x releases.
You can ftp egcs-1.0.3 either as a full release, or as diffs from the egcs-1.0.2
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
next reply other threads:[~1997-12-04 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-04 14:03 Jeffrey A Law [this message]
1997-12-04 14:03 Jaewoo Kim
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=9751.895392373@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).