From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: arnez@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org, kevinb@redhat.com, yao@codesourcery.com
Subject: Re: [RFC 02/23] Remove 'arch' field from regset structure
Date: Mon, 05 May 2014 09:32:00 -0000 [thread overview]
Message-ID: <201405050931.s459Vnbu027141@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <8738gx6bc2.fsf@br87z6lw.de.ibm.com> (message from Andreas Arnez on Mon, 28 Apr 2014 11:40:45 +0200)
> From: Andreas Arnez <arnez@linux.vnet.ibm.com>
>
> Removes the 'arch' field from the regset structure, since it
> represents the only "dynamic" data in a regset. It was referenced in
> some regset supply- and collect routines, to get access to the gdbarch
> associated with the regset. Naturally, the affected routines always
> have access to the regcache to be supplied to or collected from. Thus
> the gdbarch associated with that regcache can be used instead.
>
> gdb/
> * regset.h (struct regset): Remove gdbarch field.
> * regset.c (regset_alloc): Drop initialization of gdbarch field.
> * nios2-linux-tdep.c (nios2_core_regset): Likewise.
> * ppcfbsd-tdep.c (ppc32_fbsd_gregset, ppc64_fbsd_gregset):
> Likewise.
> * ppc-linux-tdep.c (ppc32_linux_gregset, ppc64_linux_gregset)
> (ppc32_linux_fpregset, ppc32_linux_vrregset)
> (ppc32_linux_vsxregset): Likewise.
> * i386obsd-tdep.c (i386obsd_aout_supply_regset): Get the gdbarch
> via the regcache instead of the regset.
> * i386-tdep.c (i386_supply_gregset, i386_collect_gregset)
> (i386_supply_fpregset, i386_collect_fpregset): Likewise.
> * amd64obsd-tdep.c (amd64obsd_supply_regset): Likewise.
> * amd64-tdep.c (amd64_supply_fpregset, amd64_collect_fpregset):
> Likewise.
The
> - const struct gdbarch_tdep *tdep = gdbarch_tdep (regset->arch);
> + const struct gdbarch_tdep *tdep = gdbarch_tdep (get_regcache_arch (regcache));
changes make the lines too long. I suggest changing them to:
struct gdbarch *gdbarch = get_regcache_arch (regcache);
const struct gdbarch_tdep *tdep = gdbarch_tdep(gdbarch);
Otherwise, this change is fine with me.
next prev parent reply other threads:[~2014-05-05 9:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 9:35 [RFC 00/23] Regset rework preparations Andreas Arnez
2014-04-28 9:39 ` [RFC 01/23] Constify regset structures Andreas Arnez
2014-05-05 9:45 ` Mark Kettenis
2014-04-28 9:40 ` [RFC 02/23] Remove 'arch' field from regset structure Andreas Arnez
2014-05-05 9:32 ` Mark Kettenis [this message]
2014-05-05 13:35 ` Andreas Arnez
2014-04-28 9:44 ` [RFC 03/23] AARCH64: Replace regset_alloc() invocations by static regset structures Andreas Arnez
2014-04-28 9:46 ` [RFC 04/23] ARM: " Andreas Arnez
2014-04-28 9:47 ` [RFC 05/23] X86: " Andreas Arnez
2014-04-28 15:33 ` Mark Kettenis
2014-04-29 8:58 ` Andreas Arnez
2014-04-28 9:48 ` [RFC 06/23] MIPS: " Andreas Arnez
2014-04-28 9:49 ` [RFC 07/23] MN10300: " Andreas Arnez
2014-04-28 9:50 ` [RFC 08/23] SCORE: Replace regset_alloc() invocation by a static regset structure Andreas Arnez
2014-04-28 9:51 ` [RFC 09/23] SPARC: Rename register maps from "*regset" to "*regmap" Andreas Arnez
2014-05-05 9:50 ` Mark Kettenis
2014-04-28 9:52 ` [RFC 10/23] SPARC: Replace regset_alloc() invocations by static regset structures Andreas Arnez
2014-05-05 9:52 ` Mark Kettenis
2014-04-28 9:53 ` [RFC 11/23] Drop regset_alloc() Andreas Arnez
2014-05-05 9:53 ` Mark Kettenis
2014-04-28 9:54 ` [RFC 13/23] S390: Migrate to regcache_supply/collect_regset Andreas Arnez
2014-04-28 9:54 ` [RFC 12/23] regcache: Add functions suitable for regset_supply/collect Andreas Arnez
2014-05-05 10:02 ` Mark Kettenis
2014-05-05 15:34 ` Andreas Arnez
2014-04-28 9:55 ` [RFC 14/23] AARCH64 Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-04-28 9:56 ` [RFC 15/23] ALPHA " Andreas Arnez
2014-04-28 9:57 ` [RFC 16/23] FRV " Andreas Arnez
2014-04-28 9:58 ` [RFC 17/23] HPPA " Andreas Arnez
2014-04-28 9:59 ` [RFC 18/23] M32R Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-04-28 9:59 ` [RFC 19/23] NIOS2 " Andreas Arnez
2014-04-28 10:00 ` [RFC 20/23] SCORE: " Andreas Arnez
2014-04-28 10:01 ` [RFC 22/23] M68K Linux: Define regset structures Andreas Arnez
2014-04-28 10:01 ` [RFC 21/23] TILEGX Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-04-28 10:02 ` [RFC 23/23] IA64 Linux: Define regset structures Andreas Arnez
2014-04-28 15:29 ` [RFC 00/23] Regset rework preparations Maciej W. Rozycki
2014-04-28 15:38 ` Andreas Arnez
2014-05-08 10:31 ` Andreas Arnez
2014-05-05 8:09 ` [ping] " Andreas Arnez
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=201405050931.s459Vnbu027141@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=yao@codesourcery.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