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 tree-optimization/109985] __builtin_prefetch ignored by GCC 12/13 Date: Sun, 28 May 2023 20:40:46 +0000 [thread overview] Message-ID: <bug-109985-4-PwjnT9OWLE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109985 --- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Created attachment 55180 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55180&action=edit untested patch It turns out that as modref was written for memory loads/stores only and later side effects discovery was retrofitted, I forgot to revisit code handling CONST and NOVOPS together. There are quite few places where we can not short-circuit on NOVOPS and be sure we merge in the side effects and determinism flags.
next prev parent reply other threads:[~2023-05-28 20:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-26 11:38 [Bug c++/109985] New: " pdimov at gmail dot com 2023-05-26 16:36 ` [Bug tree-optimization/109985] " pinskia at gcc dot gnu.org 2023-05-26 17:15 ` christian.mazakas at gmail dot com 2023-05-26 17:17 ` pinskia at gcc dot gnu.org 2023-05-26 17:38 ` jakub at gcc dot gnu.org 2023-05-26 22:28 ` pinskia at gcc dot gnu.org 2023-05-28 20:33 ` hubicka at gcc dot gnu.org 2023-05-28 20:40 ` hubicka at gcc dot gnu.org [this message] 2023-05-30 7:31 ` rguenth at gcc dot gnu.org 2023-05-30 7:32 ` [Bug tree-optimization/109985] [12/13/14 Regression] " 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-109985-4-PwjnT9OWLE@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: linkBe 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).