public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/46701] [C++0x] ICE in build_data_member_initialization, at cp/semantics.c:5503
Date: Fri, 10 Dec 2010 13:18:00 -0000	[thread overview]
Message-ID: <bug-46701-4-K8IYxhzMXT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46701-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paolo.carlini at oracle dot
                   |                            |com

--- Comment #13 from Paolo Carlini <paolo.carlini at oracle dot com> 2010-12-10 13:17:54 UTC ---
By the way, here and in c++/46877, the ICEs in library code - which I would
consider rather serious because prevent people from testing in C++0x mode quite
common uses of std::map - occur in a std::pair constructor decorated with
constexpr in a way not conforming to the letter of n3225. Thus, if we can't
really go through such issue in the constexpr code for 4.6.0 - because too
risky, or whatelse - I would propose removing for now the constexpr specifiers
from std::pair. Jason, what do you think?


  parent reply	other threads:[~2010-12-10 13:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29  4:38 [Bug c++/46701] New: internal compiler error: " miles at gnu dot org
2010-11-29  4:58 ` [Bug c++/46701] " miles at gnu dot org
2010-11-29  5:14 ` miles at gnu dot org
2010-11-29  5:15 ` miles at gnu dot org
2010-11-29  5:16 ` miles at gnu dot org
2010-11-29  5:16 ` miles at gnu dot org
2010-11-29  5:22 ` miles at gnu dot org
2010-11-29 14:58 ` [Bug c++/46701] [C++0x] ICE " hjl.tools at gmail dot com
2010-12-09  1:02 ` gcc at abeckmann dot de
2010-12-09 10:32 ` paolo.carlini at oracle dot com
2010-12-09 10:33 ` paolo.carlini at oracle dot com
2010-12-09 21:50 ` gcc at abeckmann dot de
2010-12-09 22:37 ` paolo.carlini at oracle dot com
2010-12-10 13:18 ` paolo.carlini at oracle dot com [this message]
2010-12-13 21:29 ` paolo.carlini at oracle dot com

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-46701-4-K8IYxhzMXT@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).