[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2014-11-19 Thread paolo.carlini at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 Paolo Carlini changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2014-11-19 Thread paolo at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #9 from paolo at gcc dot gnu.org --- Author: paolo Date: Wed Nov 19 17:40:42 2014 New Revision: 217788 URL: https://gcc.gnu.org/viewcvs?rev=217788&root=gcc&view=rev Log: /cp 2014-11-19 Paolo Carlini PR c++/55425 * constex

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2014-11-19 Thread paolo.carlini at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #8 from Paolo Carlini --- Uhm, in fact probably it should be accepted with -std=c++11 too, let's wait a second.

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2014-11-19 Thread paolo.carlini at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #7 from Paolo Carlini --- I think we can close this. The __func__ snippet now works in mainline with -std=c++14, I'm adding it to the testsuite.

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2013-06-30 Thread richard-gccbugzilla at metafoo dot co.uk
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 Richard Smith changed: What|Removed |Added CC||richard-gccbugzilla@metafoo

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2012-11-21 Thread glisse at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 Marc Glisse changed: What|Removed |Added CC||glisse at gcc dot gnu.org --- Com

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2012-11-21 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Co

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2012-11-21 Thread jakub at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #3 from Jakub Jelinek 2012-11-21 12:40:29 UTC --- 1) is not valid constexpr IMHO, as the standard says that __func__ works as if static const char __func__[] = "function-name"; has been provided, but when it is provided,

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2012-11-21 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #2 from Jonathan Wakely 2012-11-21 12:19:06 UTC --- (In reply to comment #1) > > Situation 3: __m128i type > > -- > > > > Assigning a literal value to a constexpr __m128 fails because the literal is

[Bug c++/55425] constexpr does not work in many situations (both built-in and user supplied literals)

2012-11-21 Thread redi at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55425 --- Comment #1 from Jonathan Wakely 2012-11-21 12:12:19 UTC --- (In reply to comment #0) > > A return statement is not a return statement if the returned value is __func__ > (also true for non-standard identifiers like __PRETTY_FUNCTION_