From: Per Bothner <per@bothner.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: gcc@gnu.org
Subject: Re: change the location_t type, DECL_SOURCE_LINE etc
Date: Wed, 04 Dec 2002 15:16:00 -0000 [thread overview]
Message-ID: <3DEE89ED.9000203@bothner.com> (raw)
In-Reply-To: <3DEBED4D.5070106@bothner.com>
Neil Booth wrote:
> This is great; we've been planning to do this for a while.
> But please use (or modify if you have to, though you shouldn't need
> to) line-map.c; it provides the line -> (file, line) mapping already
> for cpplib; I've wanted to get the whole compiler using it for a while.
I'm don't understand what you're suggesting. It appears to me that
the line-map stuctues are solving a different problem tham I am,
which is how to compactly represent file/line[/column] pairs[/triples].
> Also, we've discussed before squeezing line and col information into
> 32-bits and it was rejected by rth, Fergus and others. The only
> thing that would work would be a "logical character" offset in the
> translation unit, but that's a much larger and more dubious change
> IMO. Can we please stick to 32-bit lines and 16-bit columns,
> at least for now?
I really want to pack file/line[/column] pairs[/triples] into 32 bits.
However, I have a suggestion for a more complex but less size-limited
encoding it port shortly.
--
--Per Bothner
per@bothner.com http://www.bothner.com/per/
next prev parent reply other threads:[~2002-12-04 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 15:43 Per Bothner
2002-12-02 16:06 ` Gabriel Dos Reis
2002-12-02 23:19 ` Neil Booth
2002-12-04 15:16 ` Per Bothner [this message]
2002-12-04 16:19 ` Neil Booth
2002-12-04 19:44 ` Per Bothner
2002-12-04 23:09 ` Neil Booth
2002-12-03 18:36 ` Fergus Henderson
2002-12-04 11:22 ` Per Bothner
2002-12-04 21:28 ` Fergus Henderson
2002-12-04 16:29 ` Per Bothner
2002-12-04 20:03 ` Per Bothner
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=3DEE89ED.9000203@bothner.com \
--to=per@bothner.com \
--cc=gcc@gnu.org \
--cc=neil@daikokuya.co.uk \
/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).