public inbox for gcc-announce@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: gcc-announce@gcc.gnu.org
Subject: GCC 4.3.0 Released
Date: Mon, 10 Mar 2008 15:26:00 -0000	[thread overview]
Message-ID: <20080310102133.GZ24887@devserv.devel.redhat.com> (raw)

GCC 4.3.0 has been released.

GCC 4.3.0 is a major release, containing substantial new functionality
not available in GCC 4.2.x or previous GCC releases.

See:

  http://gcc.gnu.org/gcc-4.3/changes.html

for more information about changes in GCC 4.3.0.

This release is available from the FTP servers listed here:

  http://www.gnu.org/order/ftp.html

The release is in gcc/gcc-4.3.0/ subdirectory.

There is one important caveat.  It was discovered after the final release
has been made that some OS kernels on i?86 and x86_64 architectures
violate the processor specific ABI with regards to the DF flag, if a process
is interrupted with a signal while doing overlapping memmove or running some
other code with DF flag set, the signal handler might be started with DF
flag set on entry to the signal handler.  GCC 4.3.0 no longer emits cld
instructions unnecessarily, so GCC 4.3.0 compiled async signal handlers or
functions the signal handlers call that rely on DF flag being cleared
might misbehave.  This will be hopefully fixed in the kernels soon and
future GCC releases might provide an optional workaround for this bug.
Fixes for some systems:
Linux	http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e40cd10ccff3d9fbffd57b93780bee4b7b9bff51
FreeBSD	http://www.freebsd.org/cgi/query-pr.cgi?pr=121422
Hurd	http://sources.redhat.com/ml/libc-alpha/2008-03/msg00020.html

If you encounter difficulties using GCC 4.3, please do not contact me
directly.  Instead, please visit http://gcc.gnu.org for information
about getting help.

As always, a vast number of people contributed to this GCC releases --
far too many to thank individually!

                 reply	other threads:[~2008-03-10 15:26 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=20080310102133.GZ24887@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-announce@gcc.gnu.org \
    /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).