This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/84915] New: documentation: __FUNCTION__ is said by gcc-6 info to be a preprocessor macro
- From: "galex-713 at galex-713 dot eu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 16 Mar 2018 20:12:58 +0000
- Subject: [Bug c/84915] New: documentation: __FUNCTION__ is said by gcc-6 info to be a preprocessor macro
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84915
Bug ID: 84915
Summary: documentation: __FUNCTION__ is said by gcc-6 info to
be a preprocessor macro
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: galex-713@galex-713.eu
Target Milestone: ---
(info "(gcc-6) Other Builtins") says __FUNCTION__ is a preprocessor macro,
however, cpp info says it’s not. Am I missing something? do most cpp
implementation parse C code and implement it as a macro so gcc claims it is
while itself interprets it as not being one?
Look by yourselves:
-- Built-in Function: const char * __builtin_FUNCTION ()
This function is the equivalent to the preprocessor '__FUNCTION__'
macro and returns the function name the invocation of the built-in
is in.
It is not a bug of gcc but rather of its documentation, I don’t know if here is
the right place to ask…