https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80071
--- Comment #2 from Samuel Lijin ---
They are? That's a legitimate question, I'd never heard that before but I can
totally believe it; I am looking through N4606 right now, though, and can't
find anything that implies one way or another (maybe [l
Assignee: unassigned at gcc dot gnu.org
Reporter: sxlijin+gcc at gmail dot com
Target Milestone: ---
This is related to #20262, but is, I think, a much clearer example of how the
current implementation of __LINE__ is somewhat flawed.
$ cat -n bad_line_expansion.c
1
