From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-415154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 18283 invoked by alias); 13 Feb 2013 12:20:42 -0000
Received: (qmail 18216 invoked by uid 48); 13 Feb 2013 12:20:22 -0000
From: "morpheby at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54126] ICE on constexpr move ctor with const ref type instead of error
Date: Wed, 13 Feb 2013 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: morpheby at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54126-4-ZAhA5AfNEG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54126-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2013-02/txt/msg01319.txt.bz2


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

--- Comment #5 from Ilya Mikhaltsou <morpheby at gmail dot com> 2013-02-13 12:20:21 UTC ---
(In reply to comment #4)
> Created attachment 29430 [details]
> simple fail case
> 
> I think I have an even simplier test case, I guess it's the same problem (at
> least the ICE message matches). I also think that bug 51707 is actually the
> same problem.

Yes, looks like both mine and yours testcase actually do the same - they
attempt to move some constexpr to another, and gcc fails. That looks like not
implemented or buggy check for error.

bug 51707 looks to be error on correct code and possibly fails on getting
constant l-value reference.

If they are exactly the same, then the bug actually lies in contexpr reference
mechanics, and gcc fails on getting constexpr reference of any kind, not on
moving constexpr. I'll try to investigate if it is the case as soon as I have
some free time.