public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied
Date: Mon, 15 Nov 2021 22:32:02 +0000	[thread overview]
Message-ID: <bug-103223-4-W5TiT5Xuzk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103223-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
Outside of code comments only the user-visible attribute access interface is
documented in the manual.

The main difference is probably that attribute access can be added by the user
for any pair of arguments (without a limit on the number of arguments). 
Another difference is that the implicit attribute access captures the VLA
argument bounds and the [static N] specifier that tells us that array must have
at least N elements (this latter part could be used for optimization).  The
attribute access mode none means that the argument isn't dereferenced but must
point to an object of the specified size (I'm guessing that's not quite the
same as the 'x' character in fn spec).  For the common subset it might make
sense to transform attribute access to fnspec when it applies to the first N
arguments (with N being the fnspec limit).

Come to think of it, an alternate approach to solving the IPA problem with lost
attribute access might be to extend attr fnspec to encode the same things as it
and for the warnings to use fnspec instead.  The same caveat applies that not
all of what attribute access describes can be used for optimization, so the API
would have to make the distinction quite clear.

  parent reply	other threads:[~2021-11-15 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 10:05 [Bug tree-optimization/103223] New: [12 regression] Access attribute prevents IPA optimization hubicka at gcc dot gnu.org
2021-11-13 23:56 ` [Bug tree-optimization/103223] [12 regression] Access attribute dropped when ipa-sra is applied hubicka at gcc dot gnu.org
2021-11-15  9:02 ` rguenth at gcc dot gnu.org
2021-11-15 15:50 ` jamborm at gcc dot gnu.org
2021-11-15 15:58 ` jamborm at gcc dot gnu.org
2021-11-15 16:12 ` msebor at gcc dot gnu.org
2021-11-15 18:12 ` jamborm at gcc dot gnu.org
2021-11-15 20:19 ` msebor at gcc dot gnu.org
2021-11-15 21:02 ` hubicka at kam dot mff.cuni.cz
2021-11-15 22:32 ` msebor at gcc dot gnu.org [this message]
2021-11-22  7:35 ` admin at levyhsu dot com
2021-11-22  7:53 ` hubicka at kam dot mff.cuni.cz
2022-05-06  8:31 ` [Bug ipa/103223] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:23 ` [Bug ipa/103223] [12/13/14 " 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-103223-4-W5TiT5Xuzk@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).