public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/106920] -Warray-bound false positive regression with -O2 or -Os and constant address
Date: Wed, 14 Sep 2022 07:15:52 +0000	[thread overview]
Message-ID: <bug-106920-4-jwVcWAxFDr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106920-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
might be nice to have a way to declare a variable at a fixed address so the
code can become

extern hab_rvt_entry_p **entryptr __attribute__((at(0x908)));

int main() {
        hab_rvt_entry_t *a = *entryptr;
        a();
        return 0;
}

(I googled that some embedded compiler suppports 'at')

Note if you have a definition there's a workaround to declare the
variable in a custom section and use a linker script to place that
at a fixed address.  Still that doesn't allow the compiler to
optimize the access instructions.

We could honor the 'at' attribute when expanding the variable to RTL.

Such variables are going to be interesting for alias analysis btw,
so we should document it being undefined when a variables declared
with 'at' overlaps with another variable (or allocated object).

  parent reply	other threads:[~2022-09-14  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  6:44 [Bug c/106920] New: -Warray-bound false positive regression with -O2 or -Os npfhrotynz-ptnqh.myvf at noclue dot notk.org
2022-09-13  6:51 ` [Bug c/106920] " rguenth at gcc dot gnu.org
2022-09-13  7:13 ` [Bug c/106920] -Warray-bound false positive regression with -O2 or -Os and constant address npfhrotynz-ptnqh.myvf at noclue dot notk.org
2022-09-13 16:48 ` pinskia at gcc dot gnu.org
2022-09-14  7:15 ` rguenth at gcc dot gnu.org [this message]
2022-09-14  7:37 ` npfhrotynz-ptnqh.myvf at noclue dot notk.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-106920-4-jwVcWAxFDr@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).