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 14:23:09 +0000 [thread overview] Message-ID: <bug-112296-4-Ueev4yZgnU@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 ---------------------------------------------------------------------------- Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org Status|ASSIGNED |NEW CC| |jason at gcc dot gnu.org, | |rguenth at gcc dot gnu.org --- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> --- So as for the original description of this bug - it's a feature then (unless it gets clarified in another way). Sorry. I agree it's highly unintuitive and I would hope we can eventually add diagnostics for __builtin_constant_p with arguments that have side-effects. At least the documentation should be amended. Waiting for C/C++ frontend maintainers to give an ACK, then I'll propose some wording for the documentation. Btw, clang also implements the weird semantics. int g; int bar () { if (!g) abort (); return 1; } int main() { return __builtin_constant_p (bar()); } returns 0 and doesn't abort().
next prev parent reply other threads:[~2023-10-31 14:23 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 [this message] 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-Ueev4yZgnU@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).