From: Jason Merrill <jason@redhat.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Zack Weinberg <zackw@Stanford.EDU>,
Jakub Jelinek <jakub@redhat.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: cpplib: Nix -g3.
Date: Mon, 15 Jan 2001 04:14:00 -0000 [thread overview]
Message-ID: <u9snmli56p.fsf@casey.cambridge.redhat.com> (raw)
In-Reply-To: <20010114195904.B1001@daikokuya.demon.co.uk>
>>>>> "Neil" == Neil Booth <neil@daikokuya.demon.co.uk> writes:
> Jason Merrill wrote:-
>> None of the debugging backends actually use this information, so I wouldn't
>> bother if it's at all inconvenient.
> It's already doing it that way. The # 1 stuff comes out of cppmain.c
> naturally without extra code :-) The only question was should the
> lines be # 0, but if nothing uses it that can wait until something
> does.
Ah. FWIW, the dwarf2 .debug_macinfo spec requires that command-line macros
have a line number of 0 (and appear before the first DW_MACINFO_start_file
op).
Jason
next prev parent reply other threads:[~2001-01-15 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010109233506.C7013@daikokuya.demon.co.uk>
[not found] ` <20010109155204.A2032@wolery.stanford.edu>
[not found] ` <20010110000706.C10605@daikokuya.demon.co.uk>
[not found] ` <20010110041336.V1120@devserv.devel.redhat.com>
2001-01-10 13:38 ` Neil Booth
2001-01-10 15:46 ` Zack Weinberg
2001-01-10 15:59 ` Neil Booth
2001-01-11 0:57 ` Zack Weinberg
2001-01-11 10:54 ` Neil Booth
2001-01-11 20:41 ` Zack Weinberg
2001-01-14 11:52 ` Jason Merrill
2001-01-14 11:59 ` Neil Booth
2001-01-15 4:14 ` Jason Merrill [this message]
2001-01-12 5:50 David Korn
2001-01-12 14:23 ` Neil Booth
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=u9snmli56p.fsf@casey.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=neil@daikokuya.demon.co.uk \
--cc=zackw@Stanford.EDU \
/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).