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/109362] codegen adds unnecessary extra add when reading atomic member
Date: Sat, 01 Apr 2023 07:01:57 +0000	[thread overview]
Message-ID: <bug-109362-4-JcKEFXnxWO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109362-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:87d3bc53b177037699f7f8dda3a3d17e647c459d

commit r13-6966-g87d3bc53b177037699f7f8dda3a3d17e647c459d
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Apr 1 09:00:22 2023 +0200

    testsuite: Add testcase for already fixed PR [PR109362]

    This PR got fixed with r13-137.
    Add a testcase to make sure it doesn't reappear.

    2023-04-01  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/109362
            * gcc.target/i386/pr109362.c: New test.

      parent reply	other threads:[~2023-04-01  7:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 14:01 [Bug c++/109362] New: " barry.revzin at gmail dot com
2023-03-31 14:38 ` [Bug c++/109362] " barry.revzin at gmail dot com
2023-03-31 15:26 ` jakub at gcc dot gnu.org
2023-03-31 15:27 ` jakub at gcc dot gnu.org
2023-03-31 15:29 ` barry.revzin at gmail dot com
2023-04-01  7:01 ` cvs-commit at gcc dot gnu.org [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-109362-4-JcKEFXnxWO@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).