https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
--- Comment #6 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
(In reply to Dave Malcolm from comment #0)
In both cases, the In file included from hierarchies look bogus: the
files are being directly compiled, not included.
Please try
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
--- Comment #7 from Manuel López-Ibáñez manu at gcc dot gnu.org ---
(In reply to Manuel López-Ibáñez from comment #6)
(In reply to Dave Malcolm from comment #0)
In both cases, the In file included from hierarchies look bogus: the
files are
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
--- Comment #3 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-10-18
10:39:08 UTC ---
(In reply to comment #2)
This is called by default_tree_diagnostic_starter FWIW; perhaps lto1 needs
its
own implementation of this?
Maybe yes.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
--- Comment #4 from Richard Biener rguenth at gcc dot gnu.org 2012-10-18
10:40:34 UTC ---
(In reply to comment #3)
(In reply to comment #2)
This is called by default_tree_diagnostic_starter FWIW; perhaps lto1
needs its
own
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
--- Comment #5 from Manuel López-Ibáñez manu at gcc dot gnu.org 2012-10-18
11:38:33 UTC ---
(In reply to comment #4)
We stream the expanded location and allocate new line-map entries at LTO
read time.
Where?
I guess this precludes any
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54962
Manuel López-Ibáñez manu at gcc dot gnu.org changed:
What|Removed |Added
CC||manu at gcc
