public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104787] [12/13 Regression] False positive -Wreturn-type since r12-5638-ga3e75c1491cd2d50 Date: Tue, 26 Jul 2022 12:56:28 +0000 [thread overview] Message-ID: <bug-104787-4-Bn7fqxVAwz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104787-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104787 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P2 CC| |rguenth at gcc dot gnu.org --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- So the case is probably similar - without the early folding we go all the way, transforming struct FileAccessRef f; try { if (1) { return <retval> = 0; } } finally { FileAccessRef::~FileAccessRef (&f); } __builtin_trap (); to D.2402 = 0; // predicted unlikely by early return (on trees) predictor. finally_tmp.0 = 0; FileAccessRef::~FileAccessRef (&f); if (finally_tmp.0 == 1) goto <bb 4>; [INV] else goto <bb 6>; [INV] since the return-type diagnostic is before any kind of optimization it probably diagnoses this by design. Otherwise it would be appropriate to move the diagnostic to the build_ssa_passes set of diagnostic passes which could share a common VN run to mark unreachable blocks. In the end I'm currently not working on the middle-end unreachable code diagnostic so we can as well revert the frontend change causing all this fallout ...
next prev parent reply other threads:[~2022-07-26 12:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-04 15:46 [Bug c++/104787] New: [12 " marxin at gcc dot gnu.org 2022-03-04 15:46 ` [Bug c++/104787] " marxin at gcc dot gnu.org 2022-03-05 0:38 ` pinskia at gcc dot gnu.org 2022-03-28 16:06 ` [Bug middle-end/104787] " jason at gcc dot gnu.org 2022-05-06 8:32 ` [Bug middle-end/104787] [12/13 " jakub at gcc dot gnu.org 2022-06-01 19:41 ` jason at gcc dot gnu.org 2022-07-26 12:56 ` rguenth at gcc dot gnu.org [this message] 2023-01-27 19:39 ` pinskia at gcc dot gnu.org 2023-05-08 12:24 ` [Bug middle-end/104787] [12/13/14 " rguenth 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-104787-4-Bn7fqxVAwz@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).