public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nacitar at ubercpp dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67991] New: Pointer to function with internal linkage not being allowed, when it should be Date: Fri, 16 Oct 2015 17:52:00 -0000 [thread overview] Message-ID: <bug-67991-4@http.gcc.gnu.org/bugzilla/> (raw) 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."
next reply other threads:[~2015-10-16 17:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-16 17:52 nacitar at ubercpp dot com [this message] 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
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-67991-4@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: linkBe 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).