From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Michael Eager <eager@eagercon.com>,
"gdb-patches\@sourceware.org"
<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Support for Xilinx MicroBlaze
Date: Thu, 15 Oct 2009 18:04:00 -0000 [thread overview]
Message-ID: <m3oco8wn3y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3skdkwn9u.fsf@fleche.redhat.com> (Tom Tromey's message of "Thu, 15 Oct 2009 12:00:13 -0600")
Tom> How would this be done?
Tom> Users might be using an old gcc or a new one.
Joel> The only solution I see to this problem would be that users of a recent
Joel> GCC would have to use a recent GDB.
Tom> The problem is that this also implies that users stuck on an old compiler
Tom> will be stuck with an old gdb.
Just to be clear, I don't want to be a spoiler about this.
It is fine by me to move forward like this.
In fact I'd be interested to hear how gdb has dealt with this problem in
the past. I'm also sure this won't be the last time we're in this
situation.
Tom
next prev parent reply other threads:[~2009-10-15 18:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 16:32 Michael Eager
2009-10-15 16:44 ` Tom Tromey
2009-10-15 16:47 ` Joel Brobecker
2009-10-15 18:00 ` Tom Tromey
2009-10-15 18:04 ` Tom Tromey [this message]
2009-10-15 18:31 ` Joel Brobecker
2009-10-16 12:53 ` Daniel Jacobowitz
2009-10-16 16:14 ` Michael Eager
2009-10-15 17:12 ` Michael Eager
2009-10-15 17:18 ` Joel Brobecker
2009-10-15 18:06 ` Michael Eager
2009-10-15 16:46 ` Joel Brobecker
2009-10-15 17:14 ` Michael Eager
2009-10-15 19:31 ` Michael Eager
2009-10-16 7:53 ` Build-failure from " Pierre Muller
2009-10-16 15:56 ` Michael Eager
2009-10-16 16:11 ` Pierre Muller
2009-10-16 16:35 ` Joel Brobecker
2009-10-16 23:21 ` Michael Eager
-- strict thread matches above, loose matches on Subject: below --
2009-10-06 1:35 Michael Eager
2009-10-06 7:14 ` Eli Zaretskii
2009-10-14 1:47 ` Joel Brobecker
2009-10-14 17:49 ` Michael Eager
2009-10-14 17:56 ` Daniel Jacobowitz
2009-10-14 18:01 ` Michael Eager
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=m3oco8wn3y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=eager@eagercon.com \
--cc=gdb-patches@sourceware.org \
/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