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 ipa/111773] Inconsistent optimization of replaced operator new() Date: Thu, 12 Oct 2023 08:15:37 +0000 [thread overview] Message-ID: <bug-111773-4-tiKv19EZvu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111773 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-10-12 Status|UNCONFIRMED |ASSIGNED Component|c++ |ipa Ever confirmed|0 |1 CC| |hubicka at gcc dot gnu.org, | |marxin at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Keywords| |wrong-code --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- For the second case I think we do something wrong. local-pure-const figures operator new is 'noreturn': Function is locally looping. Function is locally throwing. Function is locally malloc. Function found to be noreturn: operator new and fixup_cfg in turn turns main into int main () { int * D.3130; int * p1; int * _3(D); <bb 2> : operator new (4); } which would be fine I think. But then CDDCE decides Eliminating unnecessary statements: Deleting : operator new (4); and we end up with int main () { int * D.3130; int * p1; int * _3(D); <bb 2> : } and local-pure-const adds an unreachable: local analysis of int main()/18 checking previously known:Function is locally const. Function found to be noreturn: main Function found to be const: int main()/18 Declaration updated to be const: int main()/18 Function found to be nothrow: main Introduced new external node (void __builtin_unreachable()/32). int main () { int * D.3130; int * p1; int * _3(D); <bb 2> [count: 0]: __builtin_unreachable (); I think CD-DCE shouldn't remove the call as it's looping and noreturn. It doesn't mark the allocation as necessary because of -fallocation-dce: if (callee != NULL_TREE && flag_allocation_dce && DECL_IS_REPLACEABLE_OPERATOR_NEW_P (callee)) return; we fail to check gimple_call_from_new_or_delete here I think (we later do it in most other places). But we maybe should never remove a control stmt which a noreturn call is, even more so as it can throw (yeah, we remove "dead" exceptions, but together with noreturn this doesn't quite match). Adding gimple_call_from_new_or_delete () will fix the testcase at hand but I think the same issue would exist with a class scope operator new triggered by a new expression. So, it's maybe not wrong we remove the call to ::operator new(), but if we do we have to preserve the 'return 10;' - we cannot do both, take advantage of 'noreturn' _and_ elide it. The behavior for the other testcase is OK I think.
next prev parent reply other threads:[~2023-10-12 8:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 15:59 [Bug c++/111773] New: " vlad at solidsands dot nl 2023-10-11 16:05 ` [Bug c++/111773] " pinskia at gcc dot gnu.org 2023-10-12 8:15 ` rguenth at gcc dot gnu.org [this message] 2023-10-12 8:48 ` [Bug ipa/111773] " sjames at gcc dot gnu.org 2023-10-13 6:34 ` cvs-commit at gcc dot gnu.org 2023-10-13 6:43 ` rguenth at gcc dot gnu.org 2023-10-18 14:09 ` vlad at solidsands dot nl 2023-10-19 6:16 ` 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-111773-4-tiKv19EZvu@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).