public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/60594] std::function of a type with a declared (but not defined) return type fails to compile Date: Tue, 08 Apr 2014 04:16:00 -0000 [thread overview] Message-ID: <bug-60594-4-8phAt4b5Os@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60594-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60594 Mitsuru Kariya <kariya_mitsuru at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kariya_mitsuru at hotmail dot com --- Comment #5 from Mitsuru Kariya <kariya_mitsuru at hotmail dot com> --- FYI, the BUG2 above is compiled successfully by gcc 4.7.3. cf. http://melpon.org/wandbox/permlink/UZdP4fovs2ATM2iZ Additionally, the sample code below cannot be compiled by gcc HEAD. #include <functional> struct S { std::function<S()> f; }; int main() { S l{ []{ return S{nullptr}; } }; } cf. http://melpon.org/wandbox/permlink/HAZ7i5JE94KSQhM7 It is also compiled successfully by gcc 4.7.3. And I think that struct S is not incomplete type (at least, at the point where it is used).
next prev parent reply other threads:[~2014-04-08 4:16 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-19 18:49 [Bug libstdc++/60594] New: " dblaikie at gmail dot com 2014-03-19 19:04 ` [Bug libstdc++/60594] " redi at gcc dot gnu.org 2014-03-19 19:48 ` redi at gcc dot gnu.org 2014-03-19 20:52 ` chandlerc at gmail dot com 2014-03-19 21:22 ` daniel.kruegler at googlemail dot com 2014-04-08 4:16 ` kariya_mitsuru at hotmail dot com [this message] 2014-04-08 10:07 ` redi at gcc dot gnu.org 2014-04-15 15:26 ` [Bug libstdc++/60594] [4.8/4.9/4.10 Regression] " redi at gcc dot gnu.org 2014-04-15 15:27 ` [Bug libstdc++/60594] [4.8/4.9 " redi at gcc dot gnu.org 2014-05-06 11:45 ` redi at gcc dot gnu.org 2014-05-06 13:28 ` redi at gcc dot gnu.org 2014-05-06 13:29 ` redi 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-60594-4-8phAt4b5Os@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).