From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Remove current_gdbarch register handling from symbol readers
Date: Wed, 20 May 2009 17:42:00 -0000 [thread overview]
Message-ID: <83eiujpt7n.fsf@gnu.org> (raw)
In-Reply-To: <200905201503.n4KF3ofO011061@d12av02.megacenter.de.ibm.com>
> Date: Wed, 20 May 2009 17:03:50 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
>
> this patch removes most of the remaining instances of current_gdbarch
> from the symbol readers.
Thanks.
> Tested on powerpc64-linux and amd64-linux (also with stabs).
What about the COFF related parts? were they tested?
I recently found a few places where COFF support suffered some serious
bitrot, and I think that's because it is not tested enough. Is there
some Posix platform that supports COFF, and where we could run the
test suite?
next prev parent reply other threads:[~2009-05-20 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 15:04 Ulrich Weigand
2009-05-20 17:42 ` Eli Zaretskii [this message]
2009-05-21 0:52 ` Ulrich Weigand
2009-05-21 3:27 ` Eli Zaretskii
2009-05-25 13:15 ` Ulrich Weigand
2009-05-25 20:59 ` Eli Zaretskii
2009-05-26 19:01 ` Ulrich Weigand
2009-06-04 12:36 ` Ulrich Weigand
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=83eiujpt7n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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