public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christian.mazakas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109985] __builtin_prefetch ignored by GCC 12/13
Date: Fri, 26 May 2023 17:15:53 +0000 [thread overview]
Message-ID: <bug-109985-4-M6UBW4ptqy@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
Christian Mazakas <christian.mazakas at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christian.mazakas at gmail dot com
--- Comment #2 from Christian Mazakas <christian.mazakas at gmail dot com> ---
Created attachment 55172
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55172&action=edit
Preprocessed source from the relevant godbolt.org link
This is the preprocessed output on my machine, generated using the code from
the relevant benchmark and develop Branch of Unordered
Let me know if it doesn't provide enough information or if more is required.
next prev parent reply other threads:[~2023-05-26 17:15 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 [this message]
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
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-M6UBW4ptqy@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).