From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Eliminate char buf[MAX_REGISTER_RAW_SIZE]
Date: Sun, 02 Feb 2003 05:36:00 -0000 [thread overview]
Message-ID: <3E3CAE43.5040500@redhat.com> (raw)
In-Reply-To: <3E3AFFA5.9080902@redhat.com>
> 2003-01-31 Andrew Cagney <ac131313@redhat.com>
>
> * mips-nat.c (zerobuf): Delete.
> (fetch_inferior_registers): Alloc local zerobuf.
> (fetch_core_registers): Alloc local zerobuf.
> * d10v-tdep.c (show_regs): Don't allocate a dynamic array using
> MAX_REGISTER_RAW_SIZE or MAX_REGISTER_VIRTUAL_SIZE.
> * thread-db.c (thread_db_store_registers): Ditto.
> * sh-tdep.c (sh_do_register): Ditto.
> * rom68k-rom.c (rom68k_supply_one_register): Ditto.
> * remote-sim.c (gdbsim_store_register): Ditto.
> * remote-mips.c (mips_wait, mips_fetch_registers): Ditto.
> * remote-e7000.c (fetch_regs_from_dump): Ditto.
> * monitor.c (monitor_supply_register): Ditto.
> * mipsv4-nat.c (supply_gregset, supply_fpregset): Ditto.
> * mips-nat.c (fetch_inferior_registers): Ditto.
> * m68klinux-nat.c (fetch_register): Ditto.
> * lynx-nat.c (fetch_inferior_registers): Ditto.
> (fetch_inferior_registers): Ditto.
> * irix4-nat.c (supply_gregset, supply_fpregset): Ditto.
> * hpux-thread.c (hpux_thread_fetch_registers): Ditto.
> (hpux_thread_store_registers): Ditto.
> * hppah-nat.c (fetch_register): Ditto.
> * hppab-nat.c (fetch_register): Ditto.
> * hppa-tdep.c (pa_register_look_aside): Ditto.
> (pa_print_fp_reg, pa_strcat_fp_reg): Ditto.
> * dve3900-rom.c (fetch_bitmapped_register): Ditto.
>
I've checked this in.
Andrew
next prev parent reply other threads:[~2003-02-02 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 22:58 Andrew Cagney
2003-01-31 23:20 ` Andreas Schwab
2003-01-31 23:26 ` Andrew Cagney
2003-02-01 1:36 ` Michael Snyder
2003-02-01 6:17 ` Andrew Cagney
2003-02-01 6:13 ` Joel Brobecker
2003-02-01 6:40 ` Andrew Cagney
2003-02-02 5:36 ` Andrew Cagney [this message]
2003-02-01 17:33 Michael Elizabeth Chastain
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=3E3CAE43.5040500@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.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