Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: terpstra at ito dot tu-darmstadt dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i386-linux-gnu
GCC host triplet: i386-linux-gnu
GCC target triplet: i386
--- Additional Comments From terpstra at ito dot tu-darmstadt dot de 2004-10-11
16:13 ---
Created an attachment (id=7326)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=7326action=view)
The program which demonstrates the problem
Here's what I narrowed it down to.
Compile with: gcc
--- Additional Comments From terpstra at ito dot tu-darmstadt dot de 2004-10-11
16:17 ---
Oh, and this problem doesn't occure in gcc 3.3.
However, gcc-3.3 ICEs on the larger program.
Since it at least compiles on gcc-3.4, I assume that is a different bug which
got fixed.
--
http
--- Additional Comments From terpstra at ito dot tu-darmstadt dot de 2004-10-11
17:21 ---
My bug #17934 was merged with this one.
However, my test case demonstrates the problem WITHOUT threads.
The same issue appears with a single-threaded application of sufficient complexity
--- Additional Comments From terpstra at ito dot tu-darmstadt dot de 2004-10-11
17:22 ---
This bug does not in any way involve multiple threads.
In my attached test case, gcc starts with an aligned stack and screws up the
alignment by itself.
--
What|Removed
