public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65536] LTO line number information garbled
Date: Tue, 24 Mar 2015 16:22:00 -0000	[thread overview]
Message-ID: <bug-65536-4-ks9Kceau4e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65536-4@http.gcc.gnu.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.


  parent reply	other threads:[~2015-03-24 15:35 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  7:42 [Bug lto/65536] New: [5 regression] " hubicka at gcc dot gnu.org
2015-03-24 10:15 ` [Bug lto/65536] " rguenth at gcc dot gnu.org
2015-03-24 10:15 ` [Bug lto/65536] [5 regression] " rguenth at gcc dot gnu.org
2015-03-24 12:52 ` [Bug lto/65536] " manu at gcc dot gnu.org
2015-03-24 13:32 ` rguenth at gcc dot gnu.org
2015-03-24 14:34 ` manu at gcc dot gnu.org
2015-03-24 14:42 ` manu at gcc dot gnu.org
2015-03-24 14:54 ` manu at gcc dot gnu.org
2015-03-24 16:22 ` jakub at gcc dot gnu.org [this message]
2015-03-24 16:44 ` manu at gcc dot gnu.org
2015-03-24 17:23 ` hubicka at ucw dot cz
2015-03-24 19:39 ` jakub at gcc dot gnu.org
2015-03-24 19:41 ` hubicka at gcc dot gnu.org
2015-03-24 19:51 ` manu at gcc dot gnu.org
2015-03-24 19:58 ` manu at gcc dot gnu.org
2015-03-24 20:22 ` manu at gcc dot gnu.org
2015-03-25  3:11 ` hubicka at gcc dot gnu.org
2015-03-25  3:22 ` manu at gcc dot gnu.org
2015-03-25  7:21 ` hubicka at ucw dot cz
2015-03-25  7:24 ` hubicka at ucw dot cz
2015-03-25  9:18 ` marxin at gcc dot gnu.org
2015-03-25  9:54 ` marxin at gcc dot gnu.org
2015-03-25 10:12 ` rguenth at gcc dot gnu.org
2015-03-25 10:45 ` rguenth at gcc dot gnu.org
2015-03-25 13:30 ` manu at gcc dot gnu.org
2015-03-25 18:13 ` hubicka at ucw dot cz
2015-03-25 21:40 ` hubicka at gcc dot gnu.org
2015-03-25 22:04 ` manu at gcc dot gnu.org
2015-03-25 23:36 ` manu at gcc dot gnu.org
2015-03-26  0:08 ` hubicka at gcc dot gnu.org
2015-03-26  0:19 ` manu at gcc dot gnu.org
2015-03-26  2:29 ` hubicka at ucw dot cz
2015-03-26  2:45 ` manu at gcc dot gnu.org
2015-03-26 17:49 ` manu at gcc dot gnu.org
2015-03-27  7:26 ` hubicka at gcc dot gnu.org
2015-03-27  8:11 ` hubicka at gcc dot gnu.org
2015-03-27  8:36 ` hubicka at gcc dot gnu.org
2015-03-27 15:47 ` manu at gcc dot gnu.org
2015-03-27 15:53 ` hubicka at ucw dot cz
2015-03-27 16:32 ` hubicka at ucw dot cz
2015-03-27 16:50 ` manu at gcc dot gnu.org
2015-03-27 19:39 ` hubicka at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65536-4-ks9Kceau4e@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).