public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107661] [13 Regression] lambdas get merged incorrectly in tempaltes, cause llvm-12 miscompilation Date: Sat, 12 Nov 2022 22:47:18 +0000 [thread overview] Message-ID: <bug-107661-4-ULTpisZgR5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107661 --- Comment #4 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- If I read a.cc.254t.optimized correctly I think there are two unrelated places that are expected to generate `getWaitStatesSince6.constprop`: - one is through main() - another is through seemingly_unused_foo() They have slightly different parameters, but gcc uses seemingly_unused_foo()'s one in main()'s path and as a result calls code from normally unreachable lambda.
next prev parent reply other threads:[~2022-11-12 22:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-12 18:06 [Bug middle-end/107661] New: " slyfox at gcc dot gnu.org 2022-11-12 18:13 ` [Bug middle-end/107661] " pinskia at gcc dot gnu.org 2022-11-12 18:21 ` slyfox at gcc dot gnu.org 2022-11-12 20:16 ` slyfox at gcc dot gnu.org 2022-11-12 22:47 ` slyfox at gcc dot gnu.org [this message] 2022-11-13 14:23 ` [Bug middle-end/107661] [13 Regression] lambdas get merged incorrectly in tempaltes, cause llvm-12 miscompilation since r13-3358-ge0403e95689af7 slyfox at gcc dot gnu.org 2022-11-13 14:57 ` jamborm at gcc dot gnu.org 2022-11-14 13:55 ` rguenth at gcc dot gnu.org 2022-11-15 23:21 ` slyfox at gcc dot gnu.org 2022-11-18 8:42 ` slyfox at gcc dot gnu.org 2022-11-18 8:43 ` slyfox at gcc dot gnu.org 2022-11-18 8:54 ` slyfox at gcc dot gnu.org 2022-11-19 20:11 ` slyfox at gcc dot gnu.org 2022-11-19 20:29 ` slyfox at gcc dot gnu.org 2022-11-20 21:26 ` slyfox at gcc dot gnu.org 2022-11-21 22:52 ` jamborm at gcc dot gnu.org 2022-11-22 14:13 ` [Bug ipa/107661] " jamborm at gcc dot gnu.org 2022-11-22 17:30 ` cvs-commit at gcc dot gnu.org 2022-11-22 17:33 ` jamborm at gcc dot gnu.org 2022-11-24 22:46 ` slyfox 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-107661-4-ULTpisZgR5@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).