public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mattyclarkson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/57047] [C++11] stl_pair.h:137:64: internal compiler error: Segmentation fault in constexpr constructor
Date: Tue, 23 Apr 2013 13:42:00 -0000	[thread overview]
Message-ID: <bug-57047-4-QfZ9tSCxJC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57047-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #5 from Matt Clarkson <mattyclarkson at gmail dot com> 2013-04-23 13:42:50 UTC ---
Jonathan, apologies for putting it under libstdc++ and also for putting it as a
blocker.  I didn't do that because I thought it was blocking my work but more
because I thought an ICE is a blocker for a release.  Will make sure to
remember this with any future bug reports.

I am currently trying to get this down to a nice reproducible test case. 
Currently trying to get a single main.cpp that reproduces.  Will post if I can
get that, otherwise I'll reduce the code.

Get the same error with tuple.  So I'm sure it is in the Name::Validate
constexpr function.


  parent reply	other threads:[~2013-04-23 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 12:49 [Bug libstdc++/57047] New: " mattyclarkson at gmail dot com
2013-04-23 13:19 ` [Bug c++/57047] " redi at gcc dot gnu.org
2013-04-23 13:22 ` jakub at gcc dot gnu.org
2013-04-23 13:26 ` redi at gcc dot gnu.org
2013-04-23 13:42 ` mattyclarkson at gmail dot com [this message]
2013-04-23 13:47 ` redi at gcc dot gnu.org
2013-04-23 13:53 ` mattyclarkson at gmail dot com
2013-04-23 14:07 ` mattyclarkson at gmail dot com
2013-04-23 14:17 ` mattyclarkson at gmail dot com
2013-04-23 15:10 ` [Bug c++/57047] [4.7/4.8/4.9 Regression] " jakub at gcc dot gnu.org
2013-05-10 14:36 ` 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-57047-4-QfZ9tSCxJC@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).