From: Andrew Cagney <ac131313@redhat.com>
To: Richard.Earnshaw@arm.com, Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Add support for Cirrus EP9312
Date: Mon, 10 Feb 2003 18:14:00 -0000 [thread overview]
Message-ID: <3E47E76B.2010003@redhat.com> (raw)
In-Reply-To: <200302101400.h1AE0FP06962@pc960.cambridge.arm.com>
> gdb/ChangeLog
>> 2003-02-10 Nick Clifton <nickc@redhat.com>
>>
>> * Contribute support for Cirrus Maverick ARM co-processor:
>>
>> 2000-06-02 Andrew Cagney <cagney@b1.cygnus.com>
>>
>> * remote-rdi.c (arm_rdi_fetch_registers): Add #ifdef
>> COPRO_REGNUM. Only return those registers when COPRO is
>> defined.
>
>
> This bit seems to be contrary to the multi-arch philosopy (Andrew, I'm
> surprised :-) I'd like to see this done in a way that made this code
> unconditionally present, but only activated when the CPU type was set
> appropriately.
Hey, that is almost three years ago!
Nick,
Per RichardE's comments, for this code to be accepted, it will need to
be updated to use the multi-arch framework -> no #ifdef stuff.
Andrew
prev parent reply other threads:[~2003-02-10 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 12:12 Nick Clifton
2003-02-10 14:01 ` Richard Earnshaw
2003-02-10 18:14 ` Andrew Cagney [this message]
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=3E47E76B.2010003@redhat.com \
--to=ac131313@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@redhat.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