public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110434] tree-nrv introduces incorrect CLOBBER(eol)
Date: Wed, 28 Jun 2023 13:55:25 +0000	[thread overview]
Message-ID: <bug-110434-4-mVuCxqD8kp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110434-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110434

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:4bf76b5b6db8e68755788ec91012c5a686440720

commit r14-2164-g4bf76b5b6db8e68755788ec91012c5a686440720
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jun 28 11:27:45 2023 +0200

    tree-optimization/110434 - avoid <retval> ={v} {CLOBBER} from NRV

    When NRV replaces a local variable with <retval> it also replaces
    occurences in clobbers.  This leads to <retval> being clobbered
    before the return of it which is strictly invalid but harmless in
    practice since there's no pass after NRV which would remove
    earlier stores.

    The following fixes this nevertheless.

            PR tree-optimization/110434
            * tree-nrv.cc (pass_nrv::execute): Remove CLOBBERs of
            VAR we replace with <retval>.

  parent reply	other threads:[~2023-06-28 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 10:48 [Bug tree-optimization/110434] New: " kristerw at gcc dot gnu.org
2023-06-28  9:32 ` [Bug tree-optimization/110434] " rguenth at gcc dot gnu.org
2023-06-28 13:55 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-28 13:56 ` 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-110434-4-mVuCxqD8kp@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).