public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/102306] [9/10/11/12 Regression] Volatile pointer dereferenced twice
Date: Tue, 14 Sep 2021 22:52:35 +0000	[thread overview]
Message-ID: <bug-102306-4-HWuuhvWert@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102306-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> The patch in c#5 looks good.  Since you test added_sets_0 and added_sets_1
> as well, does this mean it could happen before this patch as well?

No idea, but it seems strange to disallow the copy for i2 and not the others.

  parent reply	other threads:[~2021-09-14 22:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 11:59 [Bug rtl-optimization/102306] New: " cederman at gaisler dot com
2021-09-13 12:14 ` [Bug target/102306] " rguenth at gcc dot gnu.org
2021-09-13 12:17 ` [Bug rtl-optimization/102306] " rguenth at gcc dot gnu.org
2021-09-14 13:25 ` ebotcazou at gcc dot gnu.org
2021-09-14 13:44 ` ebotcazou at gcc dot gnu.org
2021-09-14 13:58 ` ebotcazou at gcc dot gnu.org
2021-09-14 18:35 ` [Bug rtl-optimization/102306] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-09-14 20:20 ` segher at gcc dot gnu.org
2021-09-14 20:23 ` segher at gcc dot gnu.org
2021-09-14 22:52 ` ebotcazou at gcc dot gnu.org [this message]
2021-09-15  7:17 ` ebotcazou at gcc dot gnu.org
2021-09-17  8:15 ` cvs-commit at gcc dot gnu.org
2021-09-17  8:19 ` cvs-commit at gcc dot gnu.org
2021-09-17  8:20 ` cvs-commit at gcc dot gnu.org
2021-09-17  8:23 ` cvs-commit at gcc dot gnu.org
2021-09-17  8:25 ` ebotcazou 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-102306-4-HWuuhvWert@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).