public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: gcc@gcc.gnu.org
Subject: Re: GCC 4.6.2 Release Candidate available from gcc.gnu.org
Date: Wed, 19 Oct 2011 13:32:00 -0000	[thread overview]
Message-ID: <4E9EC936.40901@embedded-brains.de> (raw)
In-Reply-To: <20111019121354.GX27949@sunsite.ms.mff.cuni.cz>

Hello,

On 10/19/2011 02:13 PM, Jakub Jelinek wrote:
[...]
> If all goes well, I'd like to release 4.6.2 in the middle of the next week.

will there be another release candidate early next week?

Is there a chance that these ARM regressions get fixed in this release?

  (A) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49641
  (B) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50106
  (C) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38644

(A) is discussed here:

http://old.nabble.com/-ARM--Fix-PR49641-td32016414.html

(B) should be fixed tomorrow according to comment in PR.

(C) is still unclear although this PR is open since 2008.

In total this makes the GCC for the older ARM7TDMI-S and ARM926EJ-S (they are 
still in production) cores pretty dangerous.

Have a nice day!

-- 
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

  reply	other threads:[~2011-10-19 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 13:31 Jakub Jelinek
2011-10-19 13:32 ` Sebastian Huber [this message]
2011-10-19 13:56   ` Jakub Jelinek
2011-10-20  7:11 ` xunxun
2011-10-22 22:42 ` Gerald Pfeifer

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=4E9EC936.40901@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=gcc@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).