public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be
@ 2015-10-16 17:52 nacitar at ubercpp dot com
2015-10-16 18:18 ` [Bug c++/67991] " nacitar at ubercpp dot com
` (5 more replies)
0 siblings, 6 replies; 7+ messages in thread
From: nacitar at ubercpp dot com @ 2015-10-16 17:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
Bug ID: 67991
Summary: Pointer to function with internal linkage not being
allowed, when it should be
Product: gcc
Version: 5.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nacitar at ubercpp dot com
Target Milestone: ---
Created attachment 36528
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36528&action=edit
test driver
Returning a function pointer from a constexpr function is leading to an error,
in a context where using the function pointer directly does in fact work. I
don't see why it should be different.
I already asked the isocpp group about this:
https://groups.google.com/a/isocpp.org/forum/embed/?place=forum/std-discussion&showsearch=true&showpopout=true&parenturl=https://isocpp.org/forums/iso-c-standard-discussion#!topic/std-discussion/OKfPmu95en4
They stated: "This is a GCC bug. Pointers to functions with internal linkage
are fine since C++11."
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
@ 2015-10-16 18:18 ` nacitar at ubercpp dot com
2015-10-16 20:16 ` pinskia at gcc dot gnu.org
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: nacitar at ubercpp dot com @ 2015-10-16 18:18 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #1 from Jacob McIntosh <nacitar at ubercpp dot com> ---
http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4268.html
This is the relevant standard change (as mentioned in the isocpp thread i
linked)
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
2015-10-16 18:18 ` [Bug c++/67991] " nacitar at ubercpp dot com
@ 2015-10-16 20:16 ` pinskia at gcc dot gnu.org
2015-10-16 20:25 ` pinskia at gcc dot gnu.org
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-10-16 20:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Are you sure this is not C++14 feature.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
2015-10-16 18:18 ` [Bug c++/67991] " nacitar at ubercpp dot com
2015-10-16 20:16 ` pinskia at gcc dot gnu.org
@ 2015-10-16 20:25 ` pinskia at gcc dot gnu.org
2015-10-16 20:30 ` nacitar at ubercpp dot com
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-10-16 20:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Try -std=c++1y or -std=c++1z .
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
` (2 preceding siblings ...)
2015-10-16 20:25 ` pinskia at gcc dot gnu.org
@ 2015-10-16 20:30 ` nacitar at ubercpp dot com
2015-10-16 20:31 ` pinskia at gcc dot gnu.org
2015-10-16 20:40 ` pinskia at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: nacitar at ubercpp dot com @ 2015-10-16 20:30 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #4 from Jacob McIntosh <nacitar at ubercpp dot com> ---
It looks like this is supposed to be a c++1y/1z feature (post c++-14 anyway)...
and it looks like it's not implemented yet in gcc. Same errors for me with
-std=c++1y and also with -std=c++1z
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
` (3 preceding siblings ...)
2015-10-16 20:30 ` nacitar at ubercpp dot com
@ 2015-10-16 20:31 ` pinskia at gcc dot gnu.org
2015-10-16 20:40 ` pinskia at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-10-16 20:31 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jacob McIntosh from comment #4)
> It looks like this is supposed to be a c++1y/1z feature (post c++-14
> anyway)... and it looks like it's not implemented yet in gcc. Same errors
> for me with -std=c++1y and also with -std=c++1z
Have you tried the trunk instead?
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug c++/67991] Pointer to function with internal linkage not being allowed, when it should be
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
` (4 preceding siblings ...)
2015-10-16 20:31 ` pinskia at gcc dot gnu.org
@ 2015-10-16 20:40 ` pinskia at gcc dot gnu.org
5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-10-16 20:40 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67991
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed on the trunk with -std=c++17 . Since this is a new feature of C++17,
it is not as important as other bugs in the C++ front-end at this stage.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2015-10-16 20:40 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-16 17:52 [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be nacitar at ubercpp dot com
2015-10-16 18:18 ` [Bug c++/67991] " nacitar at ubercpp dot com
2015-10-16 20:16 ` pinskia at gcc dot gnu.org
2015-10-16 20:25 ` pinskia at gcc dot gnu.org
2015-10-16 20:30 ` nacitar at ubercpp dot com
2015-10-16 20:31 ` pinskia at gcc dot gnu.org
2015-10-16 20:40 ` pinskia at gcc dot gnu.org
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).