diff options
| author | Richard Biener <rguenther@suse.de> | 2023-11-03 08:11:05 +0100 |
|---|---|---|
| committer | Richard Biener <rguenther@suse.de> | 2023-11-06 08:24:34 +0100 |
| commit | 442715708911ed6cc6f3785e3996a62f5ee7f21f (patch) | |
| tree | 78aabbd6ceaf76b99ed0489761cf69244597cdaf /gcc/function.cc | |
| parent | b2075291af8810794c7184fd125b991c2341cb1e (diff) | |
| download | gcc-442715708911ed6cc6f3785e3996a62f5ee7f21f.zip gcc-442715708911ed6cc6f3785e3996a62f5ee7f21f.tar.gz gcc-442715708911ed6cc6f3785e3996a62f5ee7f21f.tar.bz2 | |
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.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions