From: Richard Henderson <rth@redhat.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Geoff Keating <geoffk@redhat.com>, gcc@gcc.gnu.org
Subject: Re: problems debugging gcc
Date: Wed, 05 Dec 2001 15:43:00 -0000 [thread overview]
Message-ID: <20011205154236.A8874@redhat.com> (raw)
In-Reply-To: <20011204233807.A24275@daikokuya.demon.co.uk>; from neil@daikokuya.demon.co.uk on Tue, Dec 04, 2001 at 11:38:07PM +0000
On Tue, Dec 04, 2001 at 11:38:07PM +0000, Neil Booth wrote:
> Instead of adding a filename component and taking up more memory,
> would it be too much to switch to using a single lineno and using the
> line maps to imply the file name?
This seems like a fine idea.
r~
next prev parent reply other threads:[~2001-12-05 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 11:59 mike stump
2001-12-04 12:34 ` Neil Booth
2001-12-04 13:08 ` [c/4053] " Daniel Jacobowitz
2001-12-04 13:18 ` Neil Booth
2001-12-04 14:24 ` Geoff Keating
2001-12-04 14:31 ` Neil Booth
2001-12-04 15:27 ` Geoff Keating
2001-12-04 15:37 ` Neil Booth
2001-12-05 15:43 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-04 1:21 Danish Samad
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=20011205154236.A8874@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@redhat.com \
--cc=neil@daikokuya.demon.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).