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 tree-optimization/112296] __builtin_constant_p doesn't propagate through member functions Date: Tue, 31 Oct 2023 08:29:10 +0000 [thread overview] Message-ID: <bug-112296-4-jFBDgNTi24@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112296-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112296 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2023-10-31 Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- The issue is that we're inlining "optimized" bodies but somehow "optimize" direct() already in the frontend to ;; Function int direct(Span) (null) ;; enabled by -tree-original <<cleanup_point return <retval> = 0>>; that's because we have builtins.cc:fold_builtin_constant_p /* If this expression has side effects, show we don't know it to be a constant. Likewise if it's a pointer or aggregate type since in those case we only want literals, since those are only optimized when generating RTL, not later. And finally, if we are compiling an initializer, not code, we need to return a definite result now; there's not going to be any more optimization done. */ if (TREE_SIDE_EFFECTS (arg) || AGGREGATE_TYPE_P (TREE_TYPE (arg)) || POINTER_TYPE_P (TREE_TYPE (arg)) || cfun == 0 || folding_initializer || force_folding_builtin_constant_p) return integer_zero_node; and the CALL_EXPR we have as argument has side-effects. That all looks like from prehistoric times, but I'm only going to remove the TREE_SIDE_EFFECTS check which makes the direct and indirect cases produce the same result.
next prev parent reply other threads:[~2023-10-31 8:29 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 14:22 [Bug c++/112296] New: " barry.revzin at gmail dot com 2023-10-30 14:26 ` [Bug c++/112296] " rguenth at gcc dot gnu.org 2023-10-30 14:46 ` redi at gcc dot gnu.org 2023-10-30 14:49 ` redi at gcc dot gnu.org 2023-10-31 8:29 ` rguenth at gcc dot gnu.org [this message] 2023-10-31 9:29 ` [Bug tree-optimization/112296] " rguenth at gcc dot gnu.org 2023-10-31 9:36 ` rguenth at gcc dot gnu.org 2023-10-31 13:51 ` rth at gcc dot gnu.org 2023-10-31 13:57 ` rguenth at gcc dot gnu.org 2023-10-31 14:05 ` rth at gcc dot gnu.org 2023-10-31 14:13 ` rguenth at gcc dot gnu.org 2023-10-31 14:23 ` rguenth at gcc dot gnu.org 2023-10-31 16:55 ` joseph at codesourcery dot com 2023-11-03 7:11 ` rguenth at gcc dot gnu.org 2023-11-06 7:27 ` cvs-commit at gcc dot gnu.org 2023-11-06 7:38 ` 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-112296-4-jFBDgNTi24@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).