public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/31827] limits-exprparen.c: Pid 2297 received a SIGSEGV for stack growth failure
Date: Tue, 01 Feb 2011 17:12:00 -0000	[thread overview]
Message-ID: <bug-31827-4-O7TizxRLGH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-31827-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31827

--- Comment #13 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-02-01 17:00:26 UTC ---
Out of interest, does compiling GCC with -fsplit-stack help avoid this 
problem?  This obviously has limitations at present regarding supported 
hosts, and the need for gold as host linker to avoid problems when calling 
code built without that option, but it seems like something that option 
ought to help with.


  parent reply	other threads:[~2011-02-01 17:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-31827-4@http.gcc.gnu.org/bugzilla/>
2010-11-13  1:22 ` davek at gcc dot gnu.org
2011-02-01  4:03 ` davek at gcc dot gnu.org
2011-02-01 17:12 ` joseph at codesourcery dot com [this message]
2011-02-01 18:21 ` davek at gcc dot gnu.org
2011-03-07 19:55 ` gseanmcg at gmail dot com
2011-03-07 20:41 ` jakub at gcc dot gnu.org
2011-03-07 21:36 ` jakub at gcc dot gnu.org
2011-07-22 15:52 ` ubizjak at gmail dot com
2011-11-25 16:28 ` gseanmcg at gmail dot com
2011-11-25 17:17 ` ubizjak at gmail dot com
2007-05-04 23:03 [Bug other/31827] New: " danglin at gcc dot gnu dot org
2008-12-29  7:27 ` [Bug middle-end/31827] " pinskia at gcc dot gnu dot org
2009-07-23  6:53 ` ubizjak at gmail dot com
2009-11-03 10:23 ` bonzini at gnu dot org
2009-11-03 12:23 ` bonzini at gnu dot org
2009-11-03 18:59 ` bonzini at 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=bug-31827-4-O7TizxRLGH@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: 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).