public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd Date: Wed, 16 Mar 2022 08:58:21 +0000 [thread overview] Message-ID: <bug-103984-4-NRD6q0sK61@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103984-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103984 --- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Unfortunately the #c15 patch regressed: +FAIL: g++.dg/opt/pr80032.C -std=gnu++11 (test for excess errors) +FAIL: g++.dg/opt/pr80032.C -std=gnu++14 (test for excess errors) +FAIL: g++.dg/opt/pr80032.C -std=gnu++17 (test for excess errors) +FAIL: g++.dg/opt/pr80032.C -std=gnu++20 (test for excess errors) +FAIL: g++.dg/opt/pr80032.C -std=gnu++2b (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++11 (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++14 (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++17 (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++20 (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++2b (test for excess errors) +FAIL: g++.dg/opt/stack2.C -std=gnu++98 (test for excess errors) E.g. on stack2.C, the problem is that needs_to_live_in_memory (temp) is false before TARGET_EXPR_INITIAL is gimplified, so we don't add a clobber at all in that case with the first patch and so the stack sharing doesn't happen. This patch is a new attempt, do the TARGET_EXPR_INITIAL gimplification first, but into a temporary sequence, then push the cleanups (in the order CLOBBER first (in the end last), then asan poisioning, then TARGET_EXPR_CLEANUP, which means the opposite order later on, so first some destructors etc., then poisioning and finally a clobber).
next prev parent reply other threads:[~2022-03-16 8:58 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-11 22:18 [Bug c++/103984] New: [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 slyfox at gcc dot gnu.org 2022-01-11 22:31 ` [Bug c++/103984] " pinskia at gcc dot gnu.org 2022-01-11 22:34 ` pinskia at gcc dot gnu.org 2022-01-12 7:39 ` rguenth at gcc dot gnu.org 2022-01-12 8:29 ` jakub at gcc dot gnu.org 2022-01-26 17:48 ` [Bug c++/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329 jason at gcc dot gnu.org 2022-01-26 18:35 ` jason at gcc dot gnu.org 2022-01-26 19:03 ` jason at gcc dot gnu.org 2022-01-26 19:25 ` [Bug middle-end/103984] " jason at gcc dot gnu.org 2022-03-01 15:04 ` marxin at gcc dot gnu.org 2022-03-01 15:26 ` [Bug middle-end/103984] [12 regression] Possible maybe-uninitialized false positive on shaderc-2021.0 since r12-6329-g4f6bc28fc7dd86bd cvs-commit at gcc dot gnu.org 2022-03-15 14:22 ` jakub at gcc dot gnu.org 2022-03-15 15:06 ` jakub at gcc dot gnu.org 2022-03-15 15:16 ` jakub at gcc dot gnu.org 2022-03-15 15:55 ` jakub at gcc dot gnu.org 2022-03-15 16:55 ` jakub at gcc dot gnu.org 2022-03-15 18:00 ` jakub at gcc dot gnu.org 2022-03-16 8:47 ` jakub at gcc dot gnu.org 2022-03-16 8:58 ` jakub at gcc dot gnu.org [this message] 2022-03-17 8:26 ` cvs-commit at gcc dot gnu.org 2022-03-17 8:46 ` 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-103984-4-NRD6q0sK61@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).