public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55425] constexpr does not work in many situations  (both built-in and user supplied literals)
Date: Mon, 01 Jul 2013 06:14:00 -0000	[thread overview]
Message-ID: <bug-55425-4-OWXeIbjWWV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55425-4@http.gcc.gnu.org/bugzilla/>

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

Richard Smith <richard-gccbugzilla at metafoo dot co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richard-gccbugzilla@metafoo
                   |                            |.co.uk

--- Comment #6 from Richard Smith <richard-gccbugzilla at metafoo dot co.uk> ---
(In reply to Jonathan Wakely from comment #1)
> The standard says __func__ is a function-local variable, defined as if by
> 
> constexpr const char* x() {
>   static const char __func__[] = "function-name ";
>   return __func__;
> }
>  
> Clearly this is not a valid constexpr function.
> Changing this would be an extension.

I disagree with this. The standard doesn't say __func__ is only predefined if
it is used, so if this argument held then all constexpr functions would be
invalid.


  parent reply	other threads:[~2013-07-01  6:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 11:31 [Bug c++/55425] New: constexpr does not work in many situations (both built-in and user supplied) M8R-ug85cr at mailinator dot com
2012-11-21 12:13 ` [Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals) redi at gcc dot gnu.org
2012-11-21 12:19 ` redi at gcc dot gnu.org
2012-11-21 12:41 ` jakub at gcc dot gnu.org
2012-11-21 13:51 ` jakub at gcc dot gnu.org
2012-11-21 20:52 ` glisse at gcc dot gnu.org
2013-07-01  6:14 ` richard-gccbugzilla at metafoo dot co.uk [this message]
2014-11-19 10:27 ` paolo.carlini at oracle dot com
2014-11-19 10:37 ` paolo.carlini at oracle dot com
2014-11-19 17:41 ` paolo at gcc dot gnu.org
2014-11-19 17:43 ` 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-55425-4-OWXeIbjWWV@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).