public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/39326] Segmentation fault with -O1, out of memory with -O2 Date: Sat, 28 Feb 2009 18:10:00 -0000 [thread overview] Message-ID: <20090228181016.7266.qmail@sourceware.org> (raw) In-Reply-To: <bug-39326-13529@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from rguenth at gcc dot gnu dot org 2009-02-28 18:10 ------- One problem seems to be that we blow up the stack during GC recursing following the VUSE -> def_stmt links. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39326
next prev parent reply other threads:[~2009-02-28 18:10 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-28 15:23 [Bug c/39326] New: " sergstesh at yahoo dot com 2009-02-28 15:29 ` [Bug c/39326] " sergstesh at yahoo dot com 2009-02-28 15:32 ` sergstesh at yahoo dot com 2009-02-28 15:34 ` sergstesh at yahoo dot com 2009-02-28 17:23 ` sergstesh at yahoo dot com 2009-02-28 17:57 ` rguenth at gcc dot gnu dot org 2009-02-28 18:00 ` rguenth at gcc dot gnu dot org 2009-02-28 18:10 ` rguenth at gcc dot gnu dot org [this message] 2009-03-01 3:04 ` sergstesh at yahoo dot com 2009-03-01 3:06 ` sergstesh at yahoo dot com 2009-03-01 3:09 ` sergstesh at yahoo dot com 2009-03-01 3:54 ` sergstesh at yahoo dot com 2009-03-01 11:39 ` rguenth at gcc dot gnu dot org 2009-03-02 17:01 ` rguenth at gcc dot gnu dot org 2009-03-02 17:16 ` [Bug middle-end/39326] " pinskia at gcc dot gnu dot org 2009-03-03 13:36 ` sergstesh at yahoo dot com 2009-03-03 13:49 ` rguenther at suse dot de 2009-03-03 14:15 ` sergstesh at yahoo dot com 2009-03-17 11:05 ` rguenth at gcc dot gnu dot org 2009-03-17 12:42 ` rguenth at gcc dot gnu dot org 2009-03-17 12:59 ` rguenth at gcc dot gnu dot org 2009-03-17 13:10 ` rguenth 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=20090228181016.7266.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: linkBe 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).