public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54515] cc1plus sigsegv -O2 anonymous namespace
Date: Fri, 07 Sep 2012 11:59:00 -0000	[thread overview]
Message-ID: <bug-54515-4-Cc1IeGCAZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54515-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-09-07 11:59:45 UTC ---
(In reply to comment #3)
> Created attachment 28145 [details]
> preprocessed file as written by the sigsegv handler
> 
> Just saw a second sigsegv. This might be related to the bug (including same
> project files), but it might also be another bug.
> This compilation succeeds with -O0 and -O1, it crashes with -O3, -O2 and -Os.
> In this case there is no anonymous namespace involved.

It's the same issue.


  parent reply	other threads:[~2012-09-07 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 10:02 [Bug c++/54515] New: " werner.henze at alumni dot tu-berlin.de
2012-09-07 10:25 ` [Bug middle-end/54515] " rguenth at gcc dot gnu.org
2012-09-07 10:53 ` werner.henze at alumni dot tu-berlin.de
2012-09-07 11:49 ` werner.henze at alumni dot tu-berlin.de
2012-09-07 11:56 ` markus at trippelsdorf dot de
2012-09-07 11:59 ` markus at trippelsdorf dot de [this message]
2012-09-07 15:23 ` markus at trippelsdorf dot de
2012-09-10  9:48 ` rguenth at gcc dot gnu.org
2012-09-10  9:50 ` rguenth at gcc dot gnu.org
2012-09-10 11:33 ` rguenth at gcc dot gnu.org
2012-09-11  8:33 ` rguenth at gcc dot gnu.org
2012-09-11  8:33 ` rguenth at gcc dot gnu.org
2012-09-11  8:33 ` rguenth at gcc dot gnu.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-54515-4-Cc1IeGCAZn@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).