public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-54126-4-ZAhA5AfNEG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54126-4@http.gcc.gnu.org/bugzilla/>


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.


  parent reply	other threads:[~2013-02-13 12:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 14:17 [Bug c++/54126] New: " morpheby at gmail dot com
2012-07-30 14:22 ` [Bug c++/54126] " redi at gcc dot gnu.org
2012-07-30 14:33 ` morpheby at gmail dot com
2012-07-30 14:53 ` redi at gcc dot gnu.org
2012-07-30 14:56 ` morpheby at gmail dot com
2013-02-13  7:29 ` freddie_chopin at op dot pl
2013-02-13 12:20 ` morpheby at gmail dot com [this message]
2014-08-29 13:27 ` 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-54126-4-ZAhA5AfNEG@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).