This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/54962] Strange-looking diagnostics from diagnostic_report_current_module() from warnings emitted during LTO
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 18 Oct 2012 10:40:34 +0000
- Subject: [Bug lto/54962] Strange-looking diagnostics from diagnostic_report_current_module() from warnings emitted during LTO
- Auto-submitted: auto-generated
- References: <bug-54962-4@http.gcc.gnu.org/bugzilla/>
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 implementation of this?
> >
> > Maybe yes. LTO should print the "main" file as well (so it doesn't have
> > a MAIN_FILE_P), but not as included-from but in some other way.
> >
>
> How does the line_map works in LTO? Is it saved and restored or re-build from
> scratch?
We stream the expanded location and allocate new line-map entries at LTO
read time.