https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
--- Comment #6 from qinzhao at gcc dot gnu.org ---
(In reply to jos...@codesourcery.com from comment #5)
> We're talking about the sequence of pp-tokens in the expansion of bar(foo,
> addr), which is (foo) (addr), where foo is followed by ), not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
--- Comment #5 from joseph at codesourcery dot com ---
We're talking about the sequence of pp-tokens in the expansion of bar(foo,
addr), which is (foo) (addr), where foo is followed by ), not about the
definition.
Please take any further quest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
--- Comment #4 from qinzhao at gcc dot gnu.org ---
(In reply to jos...@codesourcery.com from comment #3)
> Macro replacement for function-like macros is defined in C17 6.10.3.
> Note in paragraph 10 the words "the function-like macro name follow
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
--- Comment #3 from joseph at codesourcery dot com ---
Macro replacement for function-like macros is defined in C17 6.10.3.
Note in paragraph 10 the words "the function-like macro name followed by a
( as the next preprocessing token". In your
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
--- Comment #2 from qinzhao at gcc dot gnu.org ---
(In reply to Joseph S. Myers from comment #1)
> This is not a bug in GCC, it's how the preprocessor is defined to work.
So, this is an user error? is there any C language rules on this?
why icc wo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91973
Joseph S. Myers changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
