public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sefi@s-e-f-i.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53599] New: gcc-4.7.1_rc20120606 segfaults compiling boost.karma
Date: Wed, 06 Jun 2012 21:43:00 -0000 [thread overview]
Message-ID: <bug-53599-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53599
Bug #: 53599
Summary: gcc-4.7.1_rc20120606 segfaults compiling boost.karma
Classification: Unclassified
Product: gcc
Version: 4.7.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: sefi@s-e-f-i.de
The attached preprocessed source makes the first release candidate of gcc-4.7
segfault, gcc-4.7.0 was fine. No additional compilation options are required. I
have just spotted this and not begun to try to reduce the testcase.
next reply other threads:[~2012-06-06 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 21:43 sefi@s-e-f-i.de [this message]
2012-06-06 21:45 ` [Bug c++/53599] " sefi@s-e-f-i.de
2012-06-07 8:06 ` [Bug c++/53599] [4.7/4.8 Regression] " jakub at gcc dot gnu.org
2012-06-07 9:15 ` sefi@s-e-f-i.de
2012-06-07 9:36 ` jakub at gcc dot gnu.org
2012-06-07 15:49 ` jason at gcc dot gnu.org
2012-06-08 6:44 ` jakub at gcc dot gnu.org
2012-06-11 9:16 ` jakub at gcc dot gnu.org
2012-06-12 12:47 ` rguenth at gcc dot gnu.org
2012-06-12 15:01 ` jason at gcc dot gnu.org
2012-06-12 18:32 ` jason at gcc dot gnu.org
2012-06-13 12:04 ` rguenth at gcc dot gnu.org
2012-06-20 7:22 ` jason 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-53599-4@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).