public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103405] [12 Regression] c67005c FAILs with -fipa-modref
Date: Wed, 24 Nov 2021 16:18:31 +0000	[thread overview]
Message-ID: <bug-103405-4-cqjPILb5Wv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103405-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 51868
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51868&action=edit
Patch in testing

Good to know that there are no more known modref & Ada problems ;)  I recently
extended modref to also handle static chains and some problem may pop out...

The problem is the IPA pass determining incorrect EAF flags for the static
chain (it get NO_INDIRECT_READ which is not true since equal reads indirectly).
This is missed propagation of EAF flags for static chain - I missed this spot
while extending retslot handling to static chain since retslots does not need
this.

  parent reply	other threads:[~2021-11-24 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 10:03 [Bug ada/103405] New: [12 Regression] c67005c FAILs rguenth at gcc dot gnu.org
2021-11-24 10:03 ` [Bug ada/103405] " rguenth at gcc dot gnu.org
2021-11-24 10:08 ` pinskia at gcc dot gnu.org
2021-11-24 10:28 ` jakub at gcc dot gnu.org
2021-11-24 10:33 ` [Bug ipa/103405] " pinskia at gcc dot gnu.org
2021-11-24 10:37 ` pinskia at gcc dot gnu.org
2021-11-24 11:02 ` pinskia at gcc dot gnu.org
2021-11-24 11:09 ` hubicka at gcc dot gnu.org
2021-11-24 11:12 ` [Bug ipa/103405] [12 Regression] c67005c FAILs with -fipa-modref ebotcazou at gcc dot gnu.org
2021-11-24 16:18 ` hubicka at gcc dot gnu.org [this message]
2021-11-25  8:30 ` hubicka at gcc dot gnu.org
2021-11-25  9:17 ` marxin 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-103405-4-cqjPILb5Wv@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).