public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "torvalds@linux-foundation.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61904] Incorrect stack red-zoning on x86-64 code generation Date: Fri, 25 Jul 2014 18:19:00 -0000 [thread overview] Message-ID: <bug-61904-4-bm9YpwAovZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61904-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #8 from Linus Torvalds <torvalds@linux-foundation.org> --- Oh, and this is marked as a duplicate of 61801, but that one is marked to be in gcc-4.8.3 The particular problem we see in kernel code generation seems to *not* happen in 4.8.3 (current fedora 20), and happens with Debian 4.9.0. So now I worry about (a) whether the duplicate bug is really true (b) or perhaps 4.8.3 really does have the same problem and we might get bitten there too, and it just happens to trigger on 4.9.0 for some otherwise unrelated reason. I'd like to have some way to tell known-bad compilers, so that we know to avoid them..
next prev parent reply other threads:[~2014-07-25 18:19 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-25 8:09 [Bug c/61904] New: " torvalds@linux-foundation.org 2014-07-25 8:11 ` [Bug c/61904] " torvalds@linux-foundation.org 2014-07-25 8:17 ` [Bug target/61904] " trippels at gcc dot gnu.org 2014-07-25 8:18 ` torvalds@linux-foundation.org 2014-07-25 8:24 ` torvalds@linux-foundation.org 2014-07-25 9:27 ` rguenth at gcc dot gnu.org 2014-07-25 9:33 ` rguenth at gcc dot gnu.org 2014-07-25 18:12 ` torvalds@linux-foundation.org 2014-07-25 18:19 ` torvalds@linux-foundation.org [this message] 2014-07-25 18:42 ` pinskia at gcc dot gnu.org 2014-07-25 19:01 ` torvalds@linux-foundation.org 2014-07-26 10:02 ` trippels 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-61904-4-bm9YpwAovZ@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: linkBe 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).