This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/35159] g++ and gfortran inoperable with no error message
- From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Feb 2008 19:50:19 -0000
- Subject: [Bug c++/35159] g++ and gfortran inoperable with no error message
- References: <bug-35159-14772@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #15 from ktietz at gcc dot gnu dot org 2008-02-16 19:50 -------
(In reply to comment #10)
> (In reply to comment #8)
> > I tested this already and it didn't solved the problem. But may +a is more
> > correct.
> Perhaps setting RTX_FRAME_RELATED_P is needed? Or gen_blockage() at some point?
As far as I saw there is a bug in ix86_expand_prologue, but it hasn't to do
something with this problem.
The code expansion for inlined static methods, seems to be broken. If I write
small test programs using alloca (and so indirect ___chkstk) every thing works
fine and the assembly is proven correct. But if the methods getting more
complex like in cp/pt.c the code gets broken. If I use the target by disabling
the stack probing most problems are gone, but still there seems to be a stack
corruption in c++ and fortan compiler. These compilers make more use of stack
allocation method alloca.
For the stack probing I am certain, that if the a linux x86_64 would enable it,
things get here broken, too. But there seems to be a issue with inline
expansion in general.
So for this bug may it the best to disable for now the stack probing at all.
Cheers, Kai
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159