[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-26 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #11 from Markus Trippelsdorf --- Here's a small (auto-)reduced testcase for this specific issue: markus@x4 ~ % cat fair.i int a, b, d; enum cpu_idle_type { CPU_MAX_IDLE_TYPES }; struct sched_domain { int balance_interval; int l

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread torva...@linux-foundation.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #10 from Linus Torvalds --- (In reply to Andrew Pinski from comment #9) > > The bad compiler versions are 4.5.0 (when debug_insn came in) to 4.8.3 and > 4.9.0 and 4.9.1. Ok, so we have no reasonable way of avoiding the problem compi

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #9 from Andrew Pinski --- (In reply to Linus Torvalds from comment #8) > 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

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread torva...@linux-foundation.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #8 from Linus Torvalds --- 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 happ

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread torva...@linux-foundation.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #7 from Linus Torvalds --- Just for completeness for the original bug report, here's the actual compiler command line that the kernel uses to generate the *.s file. gcc -Wp,-MD,kernel/sched/.fair.s.d -nostdinc -isystem /usr/lib/gc

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 Richard Biener changed: What|Removed |Added Status|WAITING |UNCONFIRMED Ever confirmed|1

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread torva...@linux-foundation.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #4 from Linus Torvalds --- As I already mentioned to Jakub Jelinek separately in the original email thread about the kernel problem: "Note that I don't personally have a reproducer (my machine has gcc-4.8.3, and I don't see the sa

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread torva...@linux-foundation.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 --- Comment #3 from Linus Torvalds --- Created attachment 33184 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33184&action=edit gzipped pre-processed fair.i file Apparently attaching a file during the initial bug entry creation failed, pr

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug target/61904] Incorrect stack red-zoning on x86-64 code generation

2014-07-25 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 Andrew Pinski changed: What|Removed |Added Component|c |target Severity|critical