public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55931] [C++11] Constexpr member function inside a static member is not working
Date: Fri, 11 Jan 2013 14:38:00 -0000	[thread overview]
Message-ID: <bug-55931-4-dztsXCsxLr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55931-4@http.gcc.gnu.org/bugzilla/>


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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-01-11
     Ever Confirmed|0                           |1
           Severity|major                       |normal

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-01-11 14:37:36 UTC ---
(In reply to comment #2)
> Should this be reported separately?

Yes please, but note this PR in the comments and vice versa, in case they turn
out to be fixed by the same change.

(In reply to comment #3)
> But this should be considered as a compiler defect, right?

Right.


  parent reply	other threads:[~2013-01-11 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  5:04 [Bug c++/55931] New: " vince.rev at gmail dot com
2013-01-10  5:18 ` [Bug c++/55931] [C++11] " pinskia at gcc dot gnu.org
2013-01-11 13:22 ` daniel.kruegler at googlemail dot com
2013-01-11 13:27 ` daniel.kruegler at googlemail dot com
2013-01-11 14:38 ` redi at gcc dot gnu.org [this message]
2013-01-11 18:32 ` daniel.kruegler at googlemail dot com
2013-02-15 19:29 ` jason at gcc dot gnu.org
2013-03-17  2:42 ` jason at gcc dot gnu.org
2013-04-01 21:05 ` jason at gcc dot gnu.org
2013-12-09 22:53 ` rmansfield at qnx 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-55931-4-dztsXCsxLr@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).