public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96184] New: GCC treats "use of local variable with automatic storage from containing function" differently in versions Date: Mon, 13 Jul 2020 12:41:24 +0000 [thread overview] Message-ID: <bug-96184-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96184 Bug ID: 96184 Summary: GCC treats "use of local variable with automatic storage from containing function" differently in versions Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: haoxintu at gmail dot com Target Milestone: --- Hi, all. This code, GCC-trunk and other versions (etc., GCC-10) treat it differently. $cat test.cc int main(){ int a = 10; int const b = 10; auto p = [ ] () noexcept ( b ? 0 : a = b) { return 0;}; return 0; } $g++-trunk -std=c++14 test.cc //nothing $g++-10 -std=c++14 test.cc test.cc: In function ‘int main()’: test.cc:4:40: error: use of local variable with automatic storage from containing function 4 | auto p = [ ] () noexcept ( b ? 0 : a = b) { return 0;}; | ^ test.cc:2:9: note: ‘int a’ declared here 2 | int a = 10; | ^ I am wondering is this a enhancement of GCC-trunk? I also test this in other GCC versions. Weirdly, only GCC-9 or GCC-10 rejects it while other versions from 6.1 to 8.3 (also trunk) accepts it. I don't know how GCC deals with this case and this also makes me confused. Thanks, Haoxin
next reply other threads:[~2020-07-13 12:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-13 12:41 haoxintu at gmail dot com [this message] 2020-07-29 3:27 ` [Bug c++/96184] " haoxintu at gmail dot com 2020-11-04 15:49 ` redi at gcc dot gnu.org 2021-09-10 6:56 ` [Bug c++/96184] [9/10 Regression] " pinskia at gcc dot gnu.org 2021-09-10 20:05 ` [Bug c++/96184] [11/12 " jason at gcc dot gnu.org 2021-09-13 2:48 ` jason at gcc dot gnu.org 2021-09-13 2:50 ` jason at gcc dot gnu.org 2022-01-08 10:46 ` pinskia at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` [Bug c++/96184] [11/12/13/14 " jakub 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-96184-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).