public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58630] [4.9 Regression] Revision 203171 breaks several MS-ABI tests
Date: Tue, 19 Nov 2013 12:22:00 -0000 [thread overview]
Message-ID: <bug-58630-4-4ZqbCs4odz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58630-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58630
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Dominique d'Humieres from comment #5)
> Sorry still present at revision 205008: see
> http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01438.html or
> http://gcc.gnu.org/ml/gcc-testresults/2013-11/msg01440.html (r204983).
>
> The difference in behavior may depend on the configure options, but I did
> not find what could be relevant.
They show up when configured with --with-arch=core2 --with-cpu=core2.
next prev parent reply other threads:[~2013-11-19 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 15:17 [Bug target/58630] New: " dominiq at lps dot ens.fr
2013-10-08 6:41 ` [Bug target/58630] " dominiq at lps dot ens.fr
2013-10-10 11:51 ` rguenth at gcc dot gnu.org
2013-11-05 14:50 ` rguenth at gcc dot gnu.org
2013-11-05 18:33 ` dominiq at lps dot ens.fr
2013-11-19 9:56 ` rguenth at gcc dot gnu.org
2013-11-19 11:47 ` dominiq at lps dot ens.fr
2013-11-19 12:22 ` hjl.tools at gmail dot com [this message]
2013-11-21 14:31 ` rguenth at gcc dot gnu.org
2013-12-15 18:16 ` [Bug testsuite/58630] " uros at gcc dot gnu.org
2013-12-15 18:17 ` ubizjak at gmail dot com
2014-02-11 19:00 ` uros at gcc dot gnu.org
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=bug-58630-4-4ZqbCs4odz@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).