https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96634
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Last reconfirmed| |2020-08-17
Resolution|WONTFIX |---
Ever confirmed|0 |1
Status|RESOLVED |NEW
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Documenting built-ins, even those meant only to be used internally, is helpful
for a number of reasons: to GCC developers ourselves not familiar with the
built-in, to users both as a heads up that they should prefer the documented
alternative and to help understand compiler messages that refer to the
built-in[1], and to implementers of third party tools such as compilers or
static analyzers who may not have access to GCC sources for IP reasons.
The Clang documentation of the built-in is below
https://clang.llvm.org/docs/LanguageExtensions.html#builtin-addressof
[*]
https://stackoverflow.com/questions/48639190/intel-icc-compile-c-code-cause-error
