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: Mon, 06 Nov 2023 07:38:52 +0000 [thread overview] Message-ID: <bug-112296-4-XbPnoZKlAJ@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 ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Keywords|documentation | CC| |jakub at gcc dot gnu.org Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org --- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> --- I clarified the documentation. While in the particular case 'span.size ()' doesn't have side-effects (well, I'm not 100% sure) in general function calls are difficult to handle "delayed" while still allowing to discard side-effects. Maybe the infrastructure we put in place for [[assume]] could help here by treating __builtin_constant_p (expr) as [["assume" (guard)]] { tem = expr; guard = __builtin_constant_p (tem); } guard; and lower it to .ASSUME (&artificial_fn, args...); but now with a return value that would become zero at the point we elide .ASSUME unless we end up with a [1,1] range for the result? That said, it's best to avoid relying on the side-effect removal, that is, avoid having arguments with possible side-effects in __builtin_constant_p.
prev parent reply other threads:[~2023-11-06 7:38 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 ` [Bug tree-optimization/112296] " rguenth at gcc dot gnu.org 2023-10-31 9:29 ` 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 [this message]
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-XbPnoZKlAJ@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).