public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107285] Incorrect code generation when we use __builtin_constant_p built-in function. Date: Mon, 17 Oct 2022 09:25:44 +0000 [thread overview] Message-ID: <bug-107285-4-nbzTtGzNm6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107285-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107285 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- No, the generated code is just fine. At -O2, bar is inlined into main. So we have unsigned int a = __builtin_constant_p (3) ? 13 : 60; and 3 is constant. In the out of line copy of bar, value1 is a function parameter, so __builtin_constant_p evaluates to false. As I said, what is bad is the testcase, the above isn't how __builtin_constant_p should be used. I'd suggest you look in /usr/include/ or other codebases how one uses the builtin...
prev parent reply other threads:[~2022-10-17 9:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-17 6:54 [Bug c/107285] New: " alex.curiou at gmail dot com 2022-10-17 7:17 ` [Bug c/107285] " jakub at gcc dot gnu.org 2022-10-17 7:40 ` alex.curiou at gmail dot com 2022-10-17 8:10 ` alex.curiou at gmail dot com 2022-10-17 9:25 ` jakub 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-107285-4-nbzTtGzNm6@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).