Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, <gdb-patches@sourceware.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH 11/12] M68K Linux: Define regset structures.
Date: Tue, 27 May 2014 01:37:00 -0000	[thread overview]
Message-ID: <5383EBE5.4060709@codesourcery.com> (raw)
In-Reply-To: <1401122208-2481-12-git-send-email-arnez@linux.vnet.ibm.com>

On 05/27/2014 12:36 AM, Andreas Arnez wrote:
> +/* Return the appropriate register set for the core section identified
> +   by SECT_NAME and SECT_SIZE.  */
> +
> +static const struct regset *
> +m68k_linux_regset_from_core_section (struct gdbarch *gdbarch,
> +				     const char *sect_name,
> +				     size_t sect_size)
> +{
> +  if (strcmp (sect_name, ".reg") == 0
> +      && sect_size >= M68K_LINUX_GREGS_SIZE)
> +    return &m68k_linux_gregset;
> +
> +  if (strcmp (sect_name, ".reg2") == 0
> +      && sect_size >= M68K_LINUX_FPREGS_SIZE)
> +    return &m68k_linux_fpregset;
> +
> +  return NULL;
> +}
> +
>  static void
>  m68k_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
>  {
> @@ -361,6 +422,10 @@ m68k_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
>  
>    set_gdbarch_skip_trampoline_code (gdbarch, find_solib_trampoline_target);
>  
> +  /* Core file support. */
> +  set_gdbarch_regset_from_core_section
> +    (gdbarch, m68k_linux_regset_from_core_section);
> +

Is it intended to include this change in this patch? or it should go
to the next patch series?

-- 
Yao (齐尧)


  reply	other threads:[~2014-05-27  1:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 16:37 [PATCH 00/12] Regset rework preparations part 2 Andreas Arnez
2014-05-26 16:37 ` [PATCH 04/12] ALPHA Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 12/12] IA64 Linux: Define " Andreas Arnez
2014-05-26 16:37 ` [PATCH 02/12] S390: Migrate to regcache_supply/collect_regset Andreas Arnez
2014-05-26 16:37 ` [PATCH 06/12] HPPA Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 09/12] SCORE: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 10/12] TILEGX Linux: " Andreas Arnez
2014-05-26 16:37 ` [PATCH 01/12] regcache: Add functions suitable for regset_supply/collect Andreas Arnez
2014-05-27  2:49   ` Yao Qi
2014-05-27 11:54     ` Andreas Arnez
2014-05-27 12:22       ` Yao Qi
2014-05-27 14:21         ` Andreas Arnez
2014-05-26 16:37 ` [PATCH 03/12] AARCH64 Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-27 21:36   ` Yufeng Zhang
2014-05-26 16:37 ` [PATCH 07/12] M32R Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-26 16:37 ` [PATCH 05/12] FRV Linux: Fill 'collect_regset' in regset structures Andreas Arnez
2014-05-26 16:37 ` [PATCH 11/12] M68K Linux: Define " Andreas Arnez
2014-05-27  1:37   ` Yao Qi [this message]
2014-05-27  8:51     ` Andreas Arnez
2014-05-27 12:48       ` Yao Qi
2014-05-26 16:37 ` [PATCH 08/12] NIOS2 Linux: Fill 'collect_regset' in regset structure Andreas Arnez
2014-05-27  2:15   ` Yao Qi
2014-06-02  9:09     ` Andreas Arnez
2014-05-27  2:56 ` [PATCH 00/12] Regset rework preparations part 2 Yao Qi
2014-05-28 17:36   ` 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=5383EBE5.4060709@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    /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