From: Andrew Cagney <ac131313@redhat.com>
To: "Martin M. Hunt" <hunt@redhat.com>, Alexandre Oliva <aoliva@redhat.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com,
"insight@sources.redhat.com" <insight@sources.redhat.com>,
gcc-patches@gcc.gnu.org, dj@redhat.com
Subject: Re: [toplevel patch] delete references to tix
Date: Tue, 11 Mar 2003 00:21:00 -0000 [thread overview]
Message-ID: <3E6D097F.2010001@redhat.com> (raw)
In-Reply-To: <1047327075.1136.18.camel@Dragon>
> On Mon, 2003-03-10 at 11:18, Alexandre Oliva wrote:
>
>
>> I don't think there's a public release that doens't include tix yet.
>> Am I mistaken? If so, I stand corrected, and the patch may very well
>> go in now.
>
>
> The last official release, gdb 5.3 had an Insight that still used tix.
> I don't recommend this version to Insight users, but I see your point
> about builds. I guess someone might still need the tix toplevel stuff;
> I just left it in out of laziness and because it didn't affect anything.
Alex wrote:
> Maybe it's a bit too early? Consider that someone might create a
> unified tree out of the latest stable releases of the tools, as
> described in the CrossGCC FAQ IIRC, and then, if it turns out that the
> insight release still uses tix, but the toplevel no longer does, we
> lose.
I think `they loose'. The senario you describe is, at this stage,
strictly hypothetical. It only occures if, at some future stage, a
binutils or gcc containing this change is made before GDB.
Besides, such edge conditions should be covered by the CrossGCC FAQ (has
that really not been changed in >3 years?).
enjoy,
Andrew
next prev parent reply other threads:[~2003-03-10 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 18:38 Nathanael Nerode
2003-03-10 19:07 ` Keith Seitz
2003-03-10 19:14 ` Alexandre Oliva
2003-03-10 19:19 ` Martin M. Hunt
2003-03-10 20:11 ` Alexandre Oliva
2003-03-10 21:54 ` Martin M. Hunt
2003-03-11 0:21 ` Andrew Cagney [this message]
2003-03-11 0:31 ` Alexandre Oliva
2003-03-11 0:38 ` Martin M. Hunt
2003-03-11 0:47 ` David Carlton
2003-03-11 14:10 ` Alexandre Oliva
2003-03-11 18:24 ` AW: " Carsten Schlote
2003-03-15 4:17 Nathanael Nerode
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=3E6D097F.2010001@redhat.com \
--to=ac131313@redhat.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hunt@redhat.com \
--cc=insight@sources.redhat.com \
--cc=neroden@twcny.rr.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).