public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "skvadrik at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/79161] possibly lost DCE / invariant motion optimization
Date: Wed, 21 Jun 2023 06:20:31 +0000 [thread overview]
Message-ID: <bug-79161-4-1adop6upKx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-79161-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79161
Ulya <skvadrik at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Ulya <skvadrik at gmail dot com> ---
> I think this is fixed for GCC 10 by r10-1052-gc29c92c789d9 (and the related patch after that which disable it for the C front-end but enables it for C++11+)
Indeed! GCC generates `return 0` as well now. Thank you Andrew.
prev parent reply other threads:[~2023-06-21 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-79161-4@http.gcc.gnu.org/bugzilla/>
2023-06-21 4:14 ` pinskia at gcc dot gnu.org
2023-06-21 6:20 ` skvadrik at gmail dot com [this message]
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-79161-4-1adop6upKx@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: link
Be 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).