public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org
Subject: Re: Better location streaming
Date: Thu, 26 May 2011 16:49:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1105261741100.9668@wotan.suse.de> (raw)
In-Reply-To: <BANLkTikg0-2h2hrqC8NvN-Hy0g1JjFO_6g@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 665 bytes --]

Hi,

On Thu, 26 May 2011, Richard Guenther wrote:

> > Hmm, I plan to optimize string streaming (since we always stream one 
> > uleb to set it is non-NULL that can be easilly handled by assigining 
> > NULL string index 0).  How precisely you however suggest to bitpack 
> > line/column and string offset together?
> 
> Similar to how you suggested, stream bits for a changed flag but instead 
> of finishing the bitpack simply stream HOST_BITS_PER_INT bits for line 

OMG, no.  Just write uleb outputters for bitpacks and use those.  In fact 
all outputs should just go through through bitpacks and properly align to 
byte border if necessary.


Ciao,
Michael.

  parent reply	other threads:[~2011-05-26 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 10:48 Jan Hubicka
2011-05-26 10:53 ` Richard Guenther
2011-05-26 11:12   ` Jan Hubicka
2011-05-26 11:24     ` Jan Hubicka
2011-05-26 11:29     ` Richard Guenther
2011-05-26 12:31       ` Jan Hubicka
2011-05-26 12:40         ` Richard Guenther
2011-05-26 12:51           ` Jan Hubicka
2011-05-26 13:20             ` Richard Guenther
2011-05-26 16:49       ` Michael Matz [this message]
2011-05-27 12:06         ` Jan Hubicka
2011-05-27 12:35           ` Richard Guenther
2011-05-27 12:40             ` Jan Hubicka

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=Pine.LNX.4.64.1105261741100.9668@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=richard.guenther@gmail.com \
    /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).