This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/65536] LTO line number information garbled
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 24 Mar 2015 15:35:34 +0000
- Subject: [Bug lto/65536] LTO line number information garbled
- Auto-submitted: auto-generated
- References: <bug-65536-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65536
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
By streaming the line_table directly you'd stream lots of location_t that are
not actually used for anything that is streamed into the LTO.
I don't understand why the tables would be huge, the string would of course use
normal LTO section string sharing, and if we stream right now every location_t
as the triplet, it would mean in case a single location_t is never used by more
than one tree we'd stream an integer extra to what we stream now (just the
triplets would be streamed in a different place), but in the more common case
where one location_t is used by many trees, we'd stream less than what we
stream now, due to the additional indirection.