Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [4/7] Modernize AIX target: inf-ptrace build fix
Date: Wed, 25 Apr 2007 01:25:00 -0000	[thread overview]
Message-ID: <200704250026.l3P0QQoV023281@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200704242205.l3OM5i1c012149@brahms.sibelius.xs4all.nl> from "Mark Kettenis" at Apr 25, 2007 12:05:44 AM

Mark Kettenis wrote:
> > Date: Tue, 24 Apr 2007 23:37:24 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > 
> > Hello,
> > 
> > this is another small build fix that is a pre-requisite for the
> > next patch (which adds inf-ptrace.c on AIX).  The problem is that
> > on AIX, PTRACE_TYPE_ARG3 is a pointer, and trying to cast a
> > CORE_ADDR directly to it gives a compile warning.
> > 
> > The patch adds an intermediate cast to "long" to fix this problem;
> > there is precedent for this method in inf_ptrace_xfer_partial.
> 
> I don't like this, but I guess this is unavoidable, I think it's more
> correct to use uintptr_t instead of long though.

I don't particularly like it either ...

Can we assume every system where inf-ptrace.c is built has uintptr_t?
I notice the type isn't frequently used elsewhere in GDB today.

If we decide to use uintptr_t, I guess the existing uses of long in
inf_ptrace_xfer_partial should be changed as well.


Bye,
Ulrich

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


  reply	other threads:[~2007-04-25  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 21:38 Ulrich Weigand
2007-04-25  0:16 ` Mark Kettenis
2007-04-25  1:25   ` Ulrich Weigand [this message]
2007-04-25  3:09     ` Daniel Jacobowitz
2007-04-26  0:15       ` Ulrich Weigand

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=200704250026.l3P0QQoV023281@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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