https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107285
--- Comment #3 from Alexey ---
(In reply to Jakub Jelinek from comment #1)
> That is just bogus expectation.
> __builtin_constant_p works that it has a cut-off after certain optimizations
> (for -O0 already very early), if optimizations before
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107285
--- Comment #2 from Alexey ---
Well, currently
The code generation is just could be wrong.
If we use the example provided: we have to see or 13 or 60 in both cases.
We have to see same result from bar function and from the final result of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107285
Bug ID: 107285
Summary: Incorrect code generation when we use
__builtin_constant_p built-in function.
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity
