From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc-linux-nat.c: Don't use regmap[] anymore.
Date: Mon, 19 Nov 2001 18:25:00 -0000 [thread overview]
Message-ID: <3C06AC88.50403@cygnus.com> (raw)
In-Reply-To: <1011129205738.ZM19235@ocotillo.lan>
> On Nov 26, 1:19pm, Elena Zannoni wrote:
>
>
>> 2001-11-26 Elena Zannoni <ezannoni@redhat.com>
>>
>> * Makefile.in (ppc-linux-nat.o): Add dependency on ppc-tdep.h.
>>
>> * ppc-tdep.h (PPC_GPLAST_REGNUM): Define.
>>
>> * ppc-linux-nat.c: Include ppc-tdep.h.
>> (ppc_register_u_addr): Don't use the static array regmap[],
>> dynamically define the mapping instead.
>> (supply_gregset): Ditto.
>> (fill_gregset): Ditto.
>> (COPY_REG): Delete macro defintion.
>> (regmap): Delete array.
>
>
> Now that I've seen Elena's WIP patch, I understand the reasons for doing
> this.
I suspect a few more targets could do with the same treatment.
Eliminating that hardwired regmap[] would probably help a few more targets.
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Elena Zannoni <ezannoni@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] ppc-linux-nat.c: Don't use regmap[] anymore.
Date: Thu, 29 Nov 2001 13:45:00 -0000 [thread overview]
Message-ID: <3C06AC88.50403@cygnus.com> (raw)
Message-ID: <20011129134500.NbeVRCzwleR0kgLgBVZenHbO7ZMxxvZKiitvyjD_DWI@z> (raw)
In-Reply-To: <1011129205738.ZM19235@ocotillo.lan>
> On Nov 26, 1:19pm, Elena Zannoni wrote:
>
>
>> 2001-11-26 Elena Zannoni <ezannoni@redhat.com>
>>
>> * Makefile.in (ppc-linux-nat.o): Add dependency on ppc-tdep.h.
>>
>> * ppc-tdep.h (PPC_GPLAST_REGNUM): Define.
>>
>> * ppc-linux-nat.c: Include ppc-tdep.h.
>> (ppc_register_u_addr): Don't use the static array regmap[],
>> dynamically define the mapping instead.
>> (supply_gregset): Ditto.
>> (fill_gregset): Ditto.
>> (COPY_REG): Delete macro defintion.
>> (regmap): Delete array.
>
>
> Now that I've seen Elena's WIP patch, I understand the reasons for doing
> this.
I suspect a few more targets could do with the same treatment.
Eliminating that hardwired regmap[] would probably help a few more targets.
Andrew
next prev parent reply other threads:[~2001-11-29 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 13:12 Elena Zannoni
2001-11-19 15:56 ` Kevin Buettner
2001-11-19 18:25 ` Andrew Cagney [this message]
2001-11-29 13:45 ` Andrew Cagney
2001-11-29 14:01 ` Kevin Buettner
2001-11-19 19:26 ` Kevin Buettner
2001-11-29 14:56 ` Andrew Cagney
2001-11-20 8:47 ` Andrew Cagney
2001-11-20 11:10 ` Kevin Buettner
2001-11-29 16:01 ` Kevin Buettner
2001-11-29 16:38 ` Andrew Cagney
2001-11-20 16:11 ` Andrew Cagney
2001-11-29 12:59 ` Kevin Buettner
2001-11-29 18:14 ` Elena Zannoni
2001-11-21 3:54 ` Elena Zannoni
2001-11-26 10:13 ` Elena Zannoni
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=3C06AC88.50403@cygnus.com \
--to=ac131313@cygnus.com \
--cc=ezannoni@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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