From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] import drow dbxread.c fix to branch
Date: Thu, 04 Apr 2002 12:18:00 -0000 [thread overview]
Message-ID: <3CACB51F.2030001@cygnus.com> (raw)
In-Reply-To: <20020404144007.A10769@nevyn.them.org>
> I'm not sure. That code assumes a different meaning of line==0 than
> the one we're using. Particularly, if I understand correctly, the
> meaning in gdbtk comes from a set of Cygnus-internal stabs for handling
> live range splitting, which never made it into any public GCC ...
``Would not be accepted into FSF's official GCC sources?''. I'm trying
to find out what the status actually is.
Andrew
next prev parent reply other threads:[~2002-04-04 20:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 21:36 Michael Elizabeth Chastain
2002-04-03 22:01 ` Daniel Jacobowitz
2002-04-04 10:58 ` Andrew Cagney
2002-04-04 11:33 ` Elena Zannoni
2002-04-04 11:40 ` Daniel Jacobowitz
2002-04-04 12:15 ` Elena Zannoni
2002-04-04 12:24 ` Daniel Jacobowitz
2002-04-04 12:18 ` Andrew Cagney [this message]
2002-04-04 12:20 ` Daniel Berlin
2002-04-04 12:30 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-04-05 13:34 Michael Elizabeth Chastain
2002-04-04 18:17 Michael Elizabeth Chastain
2002-04-04 18:36 ` Daniel Jacobowitz
2002-04-04 19:35 ` Elena Zannoni
2002-04-05 13:10 ` Jim Blandy
2002-04-05 13:16 ` Daniel Jacobowitz
2002-04-04 8:37 Michael Elizabeth Chastain
2002-04-03 20:48 Michael Elizabeth Chastain
2002-04-03 21:09 ` Daniel Jacobowitz
2002-04-01 21:36 Michael Elizabeth Chastain
2002-04-01 21:43 ` Eli Zaretskii
2002-04-03 19:43 ` Andrew Cagney
2002-04-01 11:22 Michael Elizabeth Chastain
2002-04-01 20:49 ` Eli Zaretskii
2002-04-01 8:56 Michael Elizabeth Chastain
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=3CACB51F.2030001@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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