[Bug tree-optimization/112296] __builtin_constant_p doesn't propagate through member functions

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112296

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:442715708911ed6cc6f3785e3996a62f5ee7f21f

commit r14-5143-g442715708911ed6cc6f3785e3996a62f5ee7f21f
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Nov 3 08:11:05 2023 +0100

    middle-end/112296 - __builtin_constant_p and side-effects

    The following tries to clarify the __builtin_constant_p documentation,
    stating that the argument expression is not evaluated and side-effects
    are discarded.  I'm struggling to find the correct terms matching
    what the C language standard would call things so I'd appreciate
    some help here.

    OK for trunk?

    Shall we diagnose arguments with side-effects?  It seems to me
    such use is usually unintended?  I think rather than dropping
    side-effects as a side-effect of folding the frontend should
    discard them at parsing time instead, no?

    Thanks,
    Richard.

            PR middle-end/112296
            * doc/extend.texi (__builtin_constant_p): Clarify that
            side-effects are discarded.