Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: sergiodj@br.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Improve the fetch/store of general-purpose and 	floating-point PowerPC registers
Date: Wed, 07 Jan 2009 09:56:00 -0000	[thread overview]
Message-ID: <200901070955.n079twBj014790@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <1231289020.2026.3.camel@miki> (message from 	=?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= on Tue, 06 	Jan 2009 22:43:38 -0200)

> From: =?ISO-8859-1?Q?S=E9rgio?= Durigan =?ISO-8859-1?Q?J=FAnior?= <sergiodj@br.ibm.com>
> Date: Tue, 06 Jan 2009 22:43:38 -0200
> 
> Hi guys,
> 
> Here's the new version of the patch. I've made some modifications in
> order to "follow the pattern" already established in this portion of the
> code. As a side effect, the code is cleaner now since it has less #ifdef
> statements and uses control variables to decide if a ptrace flag is
> present or not.
> 
> Thanks to Luis Machado for his valuable comments regarding this.

Hi Sergio,

Do you really need those autoconf checks for PTRACE_GETREGS & friends?
I don't see things like HAVE_PTRACE_GETREGS used in the code at all,
which makes sense since you can just check whether PTRACE_GETREGS is
defined in your code.

The reason that there are some autoconf checks for PTRACE_XXX symbols
is that at some point there were some (broken) versions of glibc that
had the PTRACE_XXX symbols as enums, but not as #defines.  But those
versions predate the introduction of PTRACE_GETREGS & friends on Linux
for PowerPC by almost a decade now.

Th reason I'm somewhat concerned with adding new autoconf checks is
that on slow systems running the autoconf checks can take quite a
while.


  reply	other threads:[~2009-01-07  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 18:32 Sérgio Durigan Júnior
2008-10-16 20:07 ` Sérgio Durigan Júnior
2009-01-07  0:44   ` Sérgio Durigan Júnior
2009-01-07  9:56     ` Mark Kettenis [this message]
2009-01-07 16:09       ` Sérgio Durigan Júnior
2009-01-08 17:46         ` Sérgio Durigan Júnior
2009-01-09 12:26           ` Luis Machado
2009-01-21 17:28             ` Sérgio Durigan Júnior
2009-04-28 20:07               ` Joel Brobecker
2009-04-29  2:16                 ` Sérgio Durigan Júnior
2009-04-29  4:05                   ` Joel Brobecker
2009-05-05 18:34                     ` Sérgio Durigan Júnior
2009-05-06 16:58                       ` Joel Brobecker
2009-05-09  3:20                         ` [PATCH] Improve the fetch/store of general-purpose andfloating-point " Sérgio Durigan Júnior
2008-11-17 23:22 ` [PATCH] Improve the fetch/store of general-purpose and floating-point " Sérgio Durigan Júnior

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=200901070955.n079twBj014790@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@br.ibm.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