public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94444] __attribute__((access(...))) ignored for memcpy when compiling with -Os
Date: Wed, 01 Apr 2020 15:49:51 +0000	[thread overview]
Message-ID: <bug-94444-4-f788NqAxhl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94444-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That makes no sense, access attribute can help for functions which GCC doesn't
know in detail what they do, but e.g. memcpy is something GCC has better
understanding of compared to what access attribute can even describe, and uses
it in various optimization passes.

  reply	other threads:[~2020-04-01 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01 15:31 [Bug c/94444] New: " felix-gcc at fefe dot de
2020-04-01 15:49 ` jakub at gcc dot gnu.org [this message]
2020-04-01 16:05 ` [Bug c/94444] " msebor at gcc dot gnu.org
2020-04-01 17:04 ` rguenth at gcc dot gnu.org
2020-04-01 17:17 ` felix-gcc at fefe dot de
2020-04-01 19:46 ` msebor 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-94444-4-f788NqAxhl@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).