Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, Ulrich.Weigand@de.ibm.com
Subject: Re: [ping 2] [RFA][PATCH v4 0/5] Add TDB regset support
Date: Mon, 15 Jul 2013 15:40:00 -0000	[thread overview]
Message-ID: <51E417DD.90806@codesourcery.com> (raw)
In-Reply-To: <87zjtnsupy.fsf@br87z6lw.de.ibm.com>

On 07/15/2013 12:34 PM, Andreas Arnez wrote:
> Luis Machado <lgustavo@codesourcery.com> writes:
>
>> I didn't go through your last update of the patch, but FTR i still
>> think we should make the core file sections static and store them in
>> some form of array instead of hardcoding their contents in numerous
>> function calls.
>
> In the PowerPC case the patch includes four call-back invocations, all
> contained in a 20-line iterator function.  I'd hardly call that
> "numerous function calls".  And I consider it an improvement over the
> original code, which had six hard-coded static array initializers with
> various copy-/pasted lines, plus the logic for selecting the correct
> array.  The improvement is even more drastic for S/390.  Don't you
> agree?  Or do you see even more potential for improvement?

What i don't see now is an obvious way of telling which register sets 
are available for core files in PowerPC. You'd have to infer that based 
on dynamic data.

It is my personal view on the change, really. I don't claim it is right 
or wrong.

Also, why is the PowerPC backend being modified together with S390? Is 
this a change to account for POWER8? The introductory mail does not 
mention anything PowerPC-specific.

Luis


  reply	other threads:[~2013-07-15 15:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 16:57 Andreas Arnez
2013-07-03 17:00 ` [RFA][PATCH v4 1/5] S/390 regmap rework Andreas Arnez
2013-07-15 14:46   ` Luis Machado
2013-07-15 17:15     ` Andreas Arnez
2013-07-03 17:02 ` [RFA][PATCH v4 2/5] S/390: Add TDB regset Andreas Arnez
2013-07-03 19:25   ` Eli Zaretskii
2013-07-03 17:04 ` [RFA][PATCH v4 3/5] Dynamic core regset sections support Andreas Arnez
2013-07-03 17:11 ` [RFA][PATCH v4 4/5] S/390: Exploit dynamic core regset sections Andreas Arnez
2013-07-03 17:21 ` [RFA][PATCH v4 5/5] PowerPC: " Andreas Arnez
2013-07-08 15:44 ` [ping] [RFA][PATCH v4 0/5] Add TDB regset support Andreas Arnez
2013-07-15  8:49   ` [ping 2] " Andreas Arnez
2013-07-15 13:27     ` Luis Machado
2013-07-15 15:34       ` Andreas Arnez
2013-07-15 15:40         ` Luis Machado [this message]
2013-07-15 16:30           ` Andreas Arnez
2013-07-16 15:26             ` Andreas Arnez
2013-07-16 16:03               ` Ulrich Weigand
2013-07-16 17:06                 ` Andreas Arnez
2013-07-15 15:58         ` Mark Kettenis

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=51E417DD.90806@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=arnez@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