Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: cseo@linux.vnet.ibm.com (Carlos Eduardo Seo)
Cc: gdb-patches@sourceware.org (GDB Patches Mailing List)
Subject: Re: [RFC] Add support for PPC Altivec registers in gcore
Date: Wed, 21 May 2008 18:46:00 -0000	[thread overview]
Message-ID: <200805211525.m4LFPhuB018406@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <48330475.1070102@linux.vnet.ibm.com> from "Carlos Eduardo Seo" at May 20, 2008 02:03:49 PM

Carlos Eduardo Seo wrote:

> Here are the patches revised. Testsuite runs show no regressions in ppc 
> and i386.

Thanks for making those changes.

> 2008-05-14  Carlos Eduardo Seo  <cseo@linux.vnet.ibm.com>
> 
> 	* gdbarch.sh: Added new gdbarch struct
> 	core_regset_sections.
> 	* gdbarch.c: Refreshed.
> 	* gdbarch.h: Refreshed.
> 	* regset.h (core_regset_section): Declared.
> 	* linux-nat.c (linux_nat_do_thread_registers): Added
> 	support to the new gdbarch struct core_regset_sections.

This should read "Added support for ...", not "to ...".

> +  /* The loop below uses the new struct core_regset_section, which stores
> +     the supported section names and sizes for the core file. Note that
Two spaces after '.' here as well, please.

> +     note PRSTATUS needs to be treated specially. But the other notes are
> +     structurally the same, so they can benefit from the new struct.  */
> +  if (core_regset_p && sect_list != NULL)
> +    while (sect_list->sect_name != NULL)
> +      {
> +	/* .reg was already handled above.  */
> +	if (strcmp (sect_list->sect_name, ".reg") == 0)
> +	  {
> +	    sect_list++;
> +	    continue;
> +	  }
> +	regset = gdbarch_regset_from_core_section (gdbarch,
> +						   sect_list->sect_name,
> +						   sect_list->size);

Please add an assertion
      gdb_assert (regset && regset->collect_regset)
here, so we don't just crash on the call below if a gdbarch doesn't
provide those functions as it should ...

> +	gdb_regset = xmalloc (sect_list->size);
> +	regset->collect_regset (regset, regcache, -1,
> +				gdb_regset, sect_list->size);
> +	note_data = (char *) elfcore_write_register_note (obfd,
> +							  note_data,
> +							  note_size,
> +							  sect_list->sect_name,
> +							  gdb_regset,
> +							  sect_list->size);
> +	xfree (gdb_regset);
> +	sect_list++;
> +      }
> +
> +  /* For architectures that does not have the struct core_regset_section
> +     implemented, we use the old method. When all the architectures have
Two spaces after '.'.


With these final changes, the patch is OK.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-05-21 15:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 22:14 Carlos Eduardo Seo
2007-10-29 19:24 ` Ulrich Weigand
2007-10-30 21:02   ` Carlos Eduardo Seo
2007-10-30 21:18     ` Ulrich Weigand
2007-10-30 21:30       ` Carlos Eduardo Seo
2007-10-30 21:31         ` Ulrich Weigand
2007-10-31 21:14           ` Carlos Eduardo Seo
2007-10-31 21:43             ` Ulrich Weigand
2008-02-08 21:42               ` Carlos Eduardo Seo
2008-02-18 18:42                 ` Ulrich Weigand
2008-02-27 17:07                   ` Carlos Eduardo Seo
2008-03-05 18:27                     ` Ulrich Weigand
2008-03-10 14:22                   ` Carlos Eduardo Seo
2008-03-17 19:07                     ` Ulrich Weigand
2008-03-20 15:31                       ` Carlos Eduardo Seo
2008-03-25 20:13                         ` Ulrich Weigand
2008-03-25 21:31                           ` Andreas Schwab
2008-03-25 21:54                             ` Ulrich Weigand
2008-03-25 22:46                               ` Carlos Eduardo Seo
2008-03-26 11:28                                 ` Ulrich Weigand
2008-03-27  1:52                       ` Carlos Eduardo Seo
2008-03-27  9:00                         ` Andreas Schwab
2008-03-27 19:54                         ` Ulrich Weigand
2008-03-28 20:41                           ` Carlos Eduardo Seo
2008-03-31 19:19                             ` Ulrich Weigand
2008-05-09 19:27                               ` Carlos Eduardo Seo
2008-05-09 20:30                                 ` Ulrich Weigand
2008-05-10  1:33                                   ` Carlos Eduardo Seo
2008-05-14  4:22                                     ` Ulrich Weigand
2008-05-20 18:41                                       ` Carlos Eduardo Seo
2008-05-21 18:46                                         ` Ulrich Weigand [this message]
2008-05-22 14:34                                           ` Carlos Eduardo Seo
2008-05-22 18:45                                             ` Ulrich Weigand
2008-05-26 16:26                                               ` Carlos Eduardo Seo
     [not found] <OF67129E0D.852FADB2-ON4125738B.0050E74D-4125738B.005102FF@de.ibm.com>
2007-11-25  4:51 ` Carlos Eduardo Seo
2007-11-26 16:09   ` Ulrich Weigand
2007-11-26 16:12     ` Carlos Eduardo Seo

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=200805211525.m4LFPhuB018406@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=cseo@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.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