public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35159] g++ and gfortran inoperable with no error message
Date: Sat, 16 Feb 2008 19:51:00 -0000	[thread overview]
Message-ID: <20080216195019.32108.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35159-14772@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2008-02-16 19:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  7:38 [Bug c++/35159] New: g++ " nightstrike at gmail dot com
2008-02-11  7:40 ` [Bug c++/35159] " nightstrike at gmail dot com
2008-02-11 14:52 ` rguenth at gcc dot gnu dot org
2008-02-11 14:57 ` ktietz at gcc dot gnu dot org
2008-02-14  1:54 ` nightstrike at gmail dot com
2008-02-14  7:00 ` mmitchel at gcc dot gnu dot org
2008-02-14  8:16 ` jakub at gcc dot gnu dot org
2008-02-14  9:08 ` ktietz at gcc dot gnu dot org
2008-02-14  9:19 ` ubizjak at gmail dot com
2008-02-14  9:27 ` ktietz at gcc dot gnu dot org
2008-02-14  9:33 ` rguenth at gcc dot gnu dot org
2008-02-14  9:39 ` ubizjak at gmail dot com
2008-02-14 10:04 ` ktietz at gcc dot gnu dot org
2008-02-14 14:28 ` nightstrike at gmail dot com
2008-02-14 14:29 ` nightstrike at gmail dot com
2008-02-16 17:23 ` [Bug c++/35159] g++ and gfortran " nightstrike at gmail dot com
2008-02-16 19:51 ` ktietz at gcc dot gnu dot org [this message]
2008-03-06  3:01 ` nightstrike at gmail dot com
2008-03-06  4:51 ` jvdelisle at gcc dot gnu dot org
2008-03-06  5:10 ` nightstrike at gmail dot com
2008-03-06 16:09 ` nightstrike at gmail dot com
2008-03-08  6:06 ` jvdelisle at gcc dot gnu dot org
2008-05-13 13:24 ` nightstrike at gmail dot com
2008-09-21 15:03 ` pepalogik at seznam dot cz
2008-09-21 17:08 ` nightstrike at gmail dot com
2008-10-20 11:25 ` ktietz at gcc dot gnu dot org
2009-06-24 10:28 ` ktietz at gcc dot gnu dot 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=20080216195019.32108.qmail@sourceware.org \
    --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).