[Bug c/70257] #line incorrectly handled in error messages

[pinskia at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70257

Andrew Pinski  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #4 from Andrew Pinski  ---
Dup of bug 79106 since that seems like it has a patch.

Also note both EDG and clang is able to handle this correctly.

*** This bug has been marked as a duplicate of bug 79106 ***

[Bug c/70257] #line incorrectly handled in error messages

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70257

--- Comment #3 from Eric Gallager  ---
(In reply to Manuel López-Ibáñez from comment #2)
> I think this is a dup of bug 79106.
> 

...or possibly the other way around? Since that one is newer...

> The caret line is printed by reopening the file and counting 3 lines because
> the line directive is believed by GCC to point to the actual source code.

[Bug c/70257] #line incorrectly handled in error messages

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70257

Manuel López-Ibáñez  changed:

   What|Removed |Added

 CC||manu at gcc dot gnu.org

--- Comment #2 from Manuel López-Ibáñez  ---
I think this is a dup of bug 79106.

The caret line is printed by reopening the file and counting 3 lines because
the line directive is believed by GCC to point to the actual source code.

[Bug c/70257] #line incorrectly handled in error messages

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70257

Eric Gallager  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2017-07-29
 CC||egallager at gcc dot gnu.org
 Ever confirmed|0   |1

--- Comment #1 from Eric Gallager  ---
Confirming that this happens; I had it happen to me in something else with
#line directives but I assumed I was just generating them wrong...