public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dev.lists at jessamine dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47950] [4.6 Regression] [C++0x] Internal compiler error: non-dependent declaration as condition causes tsubst_copy_and_build assertion failure.
Date: Wed, 02 Mar 2011 16:30:00 -0000 [thread overview]
Message-ID: <bug-47950-4-zdfIkE9Dji@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47950-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47950
--- Comment #3 from Adam Butcher <dev.lists at jessamine dot co.uk> 2011-03-02 16:30:30 UTC ---
(In reply to comment #1)
>
> Rolling back to my previous HEAD reveals that the reduced example above still
> fails whereas the code I was originally trying to build worked. So obviously
> my reduction has changed something.
>
Okay. My original reduction was okay but I also added additional examples that
yielded the same assertion failure (obviously via different route!). The
function-call case following is the one that causes the failure in
non-dependent use of boost.foreach on the latest 4.6 HEAD. It compiles okay on
my 4.6 build from last week (prior to 170488).
if (from_int<int> x = via_function(7))
;
The constructor cases below have failed for a much longer time (though are okay
in 4.5).
if (empty<int> x = empty<int>())
;
if (from_int<int> x = from_int<int>(7))
;
So the only recent regression is the function-call case. But all cases are all
still legitimate 4.5 -> 4.6 regressions.
Before rev 170488 (25th Feb) the function-call case compiled.
I don't know when the constructor cases stopped working -- I went quite a way
back and they still failed.
next prev parent reply other threads:[~2011-03-02 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 11:21 [Bug c++/47950] New: " dev.lists at jessamine dot co.uk
2011-03-02 15:39 ` [Bug c++/47950] " dev.lists at jessamine dot co.uk
2011-03-02 16:08 ` [Bug c++/47950] [4.6 Regression] " redi at gcc dot gnu.org
2011-03-02 16:30 ` dev.lists at jessamine dot co.uk [this message]
2011-03-02 22:46 ` jason at gcc dot gnu.org
2011-03-03 2:49 ` jason at gcc dot gnu.org
2011-03-03 8:47 ` dev.lists at jessamine dot co.uk
2011-03-03 16:51 ` 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-47950-4-zdfIkE9Dji@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).