Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] gdb_stdint.h.
Date: Mon, 15 May 2006 17:16:00 -0000	[thread overview]
Message-ID: <20060515171201.GD385@nevyn.them.org> (raw)
In-Reply-To: <20060505172713.GF31029@nevyn.them.org>

On Fri, May 05, 2006 at 01:27:13PM -0400, Daniel Jacobowitz wrote:
> You want uintptr_t?  I got your uintptr_t right here.
> 
> This patch creates a header in the build directory named gdb_stdint.h.
> It defines all of the things which a stdint.h ought to define.  It uses
> the system's stdint.h if there is one, and provides anything missing,
> up to and including the whole file.
> 
> There is, of course, a huge hairy chunk of m4 and portability knowledge
> that you don't see in this patch.  That's because it's already in
> config/ and was written for GCC.  I'm OK with that :-)  It means it's
> quite well tested at this point.
> 
> This would be enough to allow us to start using uint64_t, uintptr_t,
> et cetera in the common code of GDB.  Which, in my opinion, would be a
> good idea.  They're nice to have around.
> 
> Any comments?

> 2006-05-05  Daniel Jacobowitz  <dan@codesourcery.com>
> 
> 	* configure.ac: Use GCC_HEADER_STDINT.
> 	* acinclude.m4: Include stdint.m4.
> 	* Makefile.in (gdb_stdint_h): Define.
> 	(distclean): Remove gdb_stdint.h.
> 	(Makefile, stamp-h): Update rules to generate only the correct
> 	files.
> 	(gdb_stdint.h, stamp-int): New rules.
> 	* config.in, configure: Regenerated.

Comments sounded supportive to me!  I have committed it.

Debian unstable appears to have gone up to autoconf 2.59d, so configure
has changed a bit with this commit; I think there won't be any
problems that affect GDB, but please do let me know if I'm wrong.



-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2006-05-15 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 17:27 Daniel Jacobowitz
2006-05-05 19:32 ` Jim Blandy
2006-05-05 21:50   ` Eli Zaretskii
2006-05-05 21:57     ` Michael Snyder
2006-05-15 17:16 ` Daniel Jacobowitz [this message]

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=20060515171201.GD385@nevyn.them.org \
    --to=drow@false.org \
    --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