public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ed at catmur dot co.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66476] New: Erroneous initializer_list lifetime extension from temporary initializer_list Date: Tue, 09 Jun 2015 16:49:00 -0000 [thread overview] Message-ID: <bug-66476-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66476 Bug ID: 66476 Summary: Erroneous initializer_list lifetime extension from temporary initializer_list Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ed at catmur dot co.uk Target Milestone: --- #include <stdio.h> #include <initializer_list> struct S { S(int) { puts("S(int)"); } ~S() { puts("~S()"); } }; int main() { std::initializer_list<S> ss({42}); // note extra parentheses puts("main"); } Expected output (clang 3.7, MSVC 18.00.21005.1): S(int) ~S() main Observed output (gcc 5.1.0): S(int) main ~S() The same behaviour is observed when the temporary initializer_list is made explicit: std::initializer_list<S> ss = std::initializer_list<S>{42}; Again, gcc lifetime-extends the backing array; MSVC and clang do not.
next reply other threads:[~2015-06-09 16:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-09 16:49 ed at catmur dot co.uk [this message] 2015-06-09 16:53 ` [Bug c++/66476] " 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-66476-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).