public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia 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: Fri, 26 May 2023 22:28:56 +0000 [thread overview] Message-ID: <bug-109985-4-gv7CXVH77v@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 #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Hmm: modref analyzing 'void boost::unordered::detail::foa::prefetch(const void*)/3452' (ipa=0) (pure) Analyzing flags of ssa name: p_1(D) Analyzing stmt: __builtin_prefetch (p_1(D)); current flags of p_1(D) no_direct_clobber no_indirect_clobber no_direct_escape no_indirect_escape not_returned_directly not_returned_indirectly no_direct_read no_indirect_read flags of ssa name p_1(D) no_direct_clobber no_indirect_clobber no_direct_escape no_indirect_escape not_returned_directly not_returned_indirectly no_direct_read no_indirect_read Always executed bbbs (assuming return or EH): 2 - Analyzing call:__builtin_prefetch (p_1(D)); - ECF_CONST | ECF_NOVOPS, ignoring all stores and all loads except for args. Function found to be const: void boost::unordered::detail::foa::prefetch(const void*)/3452 Declaration updated to be const: void boost::unordered::detail::foa::prefetch(const void*)/3452 - modref done with result: tracked. loads: stores: Try dse parm 0 flags: not_returned_directly not_returned_indirectly no_direct_read no_indirect_read void boost::unordered::detail::foa::prefetch (const void * p) { <bb 2> [local count: 1073741824]: __builtin_prefetch (p_1(D)); return; } Maybe that explains it, DEF_GCC_BUILTIN (BUILT_IN_PREFETCH, "prefetch", BT_FN_VOID_CONST_PTR_VAR, ATTR_NOVOPS_LEAF_LIST)
next prev parent reply other threads:[~2023-05-26 22:28 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 [this message] 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-gv7CXVH77v@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).