public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.abdurachmanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55753] [C++11][4.7/4.8 Regression] ICE constexpr ctor, tsubst_copy_and_build, at cp/pt.c:14336
Date: Mon, 24 Dec 2012 12:48:00 -0000	[thread overview]
Message-ID: <bug-55753-4-qOKXHdxSs8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55753-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #4 from David Abdurachmanov <david.abdurachmanov at gmail dot com> 2012-12-24 12:48:01 UTC ---
I did some more testing of the trunk. Compiles fine with r173678 [g++ (GCC)
4.7.0 20110511 (experimental)], but starts ICE'ing with r173679. gcc_assert
(TREE_CONSTANT (t)); (ICE line) was added in r166592 [1]. I tried passing
--enable-checking=none or touching gcc/DEV-PHASE, but bootstrap comparison was
always failing.

I looked at gcc/configure.ac. trunk has DEV-PHASE set to experimental thus
ac_checking_flags=yes, which sets ac_checking=1. If ac_checking_flags=release
then ac_checking= is not set. If ac_checking is set, it defines ENABLE_CHECKING
macro, I believe. That would probably explain why it works for me with 4.7.2
(final).

Probably this is the part [2] causing the ICE.

Merry Christmas in advance!
david

[1]
http://gcc.gnu.org/viewcvs/trunk/gcc/cp/pt.c?r1=166592&r2=166591&pathrev=166592
[2]
http://gcc.gnu.org/viewcvs/trunk/gcc/cp/pt.c?r1=173679&r2=173678&pathrev=173679


  parent reply	other threads:[~2012-12-24 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 13:06 [Bug c++/55753] New: [C++11][4.8 " david.abdurachmanov at gmail dot com
2012-12-20 13:55 ` [Bug c++/55753] " rguenth at gcc dot gnu.org
2012-12-20 14:51 ` [Bug c++/55753] [C++11][4.7/4.8 " jakub at gcc dot gnu.org
2012-12-20 14:53 ` jakub at gcc dot gnu.org
2012-12-23 12:31 ` david.abdurachmanov at gmail dot com
2012-12-24 12:48 ` david.abdurachmanov at gmail dot com [this message]
2013-01-03 20:38 ` jason at gcc dot gnu.org
2013-01-03 20:38 ` jason at gcc dot gnu.org
2013-01-03 20:43 ` jason at gcc dot gnu.org
2013-01-04 11:31 ` david.abdurachmanov at gmail dot com
2013-01-04 11:33 ` david.abdurachmanov at gmail dot com
2013-01-05 23:36 ` paolo.carlini at oracle dot com
2013-01-07 15:40 ` rguenth at gcc dot gnu.org
2013-01-07 18:01 ` jason at gcc dot gnu.org
2013-01-08 18:57 ` 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-55753-4-qOKXHdxSs8@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).