public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kristerw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110434] New: tree-nrv introduces incorrect CLOBBER(eol)
Date: Tue, 27 Jun 2023 10:48:55 +0000	[thread overview]
Message-ID: <bug-110434-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 110434
           Summary: tree-nrv introduces incorrect CLOBBER(eol)
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kristerw at gcc dot gnu.org
  Target Milestone: ---

The tree-nrv pass may introduce incorrect CLOBBER(eol) of the form
  <retval> ={v} {CLOBBER(eol)};
  return <retval>;

One example of this can be seen by compiling gcc.c-torture/execute/921204-1.c
for x86 using the flags "-O -m32", where it changes the IR

  union bu o;
  ...
  o = i;
  MEM[(union  *)&o].b18 = _11;
  MEM[(union  *)&o].b20 = _11;
  <retval> = o;
  o ={v} {CLOBBER(eol)};
  return <retval>;

to just use <retval> instead of o

  union bu o [value-expr: <retval>];
  ...
  <retval> = i;
  MEM[(union  *)&<retval>].b18 = _11;
  MEM[(union  *)&<retval>].b20 = _11;
  <retval> ={v} {CLOBBER(eol)};
  return <retval>;

so the CLOBBER(eol) now refers to <retval>.

             reply	other threads:[~2023-06-27 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 10:48 kristerw at gcc dot gnu.org [this message]
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
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@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).