From: Pedro Alves <palves@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
gdb-patches@sourceware.org
Subject: Re: New ARI warning Wed May 23 01:55:03 UTC 2012
Date: Wed, 23 May 2012 15:27:00 -0000 [thread overview]
Message-ID: <4FBD01B0.5050108@redhat.com> (raw)
In-Reply-To: <CADPb22QN5FVuh9Rtc4eqz8A9DM1-Gk+qnf2=PzfzSuNYOmgrmw@mail.gmail.com>
On 05/23/2012 04:01 PM, Doug Evans wrote:
> For reference sake,
> An alternative is to use {,u}int64_t, does ARI have any rule on them?
If there is, it's outdated. We pick up stdint.h/inttypes.h from gnulib, so
those types are now available on all hosts. If not, it's a gnulib problem.
I suggest to use those types, because libiberty itself has recently
began assuming uintptr_t through either stdint.h or inttypes.h is available.
<http://gcc.gnu.org/ml/gcc-patches/2012-04/msg00292.html>
I see no reason to consider 128 types in a libiberty header/interface at
this point. It'll be a long while (decades?) before that could be
considered portable.
> It's been in use in at least findcmd.c since gdb 7.0 [IIUC]
> (perhaps errantly, but nevertheless ...).
--
Pedro Alves
next prev parent reply other threads:[~2012-05-23 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 1:55 GDB Administrator
2012-05-23 4:18 ` Sergio Durigan Junior
2012-05-23 7:10 ` Doug Evans
2012-05-23 7:27 ` Doug Evans
2012-05-23 8:19 ` Pierre Muller
2012-05-23 14:45 ` Sergio Durigan Junior
[not found] ` <4fbc9d77.0853b40a.641e.ffff90dbSMTPIN_ADDED@mx.google.com>
2012-05-23 14:46 ` Doug Evans
2012-05-23 15:01 ` Doug Evans
2012-05-23 15:27 ` Pedro Alves [this message]
2012-05-24 18:55 ` Tom Tromey
2012-05-28 20:44 ` Mark Kettenis
2012-05-28 21:59 ` Joel Brobecker
2012-05-29 13:29 ` Maciej W. Rozycki
2012-06-22 16:05 ` Tom Tromey
2012-06-22 17:19 ` Joel Brobecker
2012-06-22 17:31 ` Joel Brobecker
2012-06-22 17:41 ` Tom Tromey
2012-06-22 19:02 ` Joel Brobecker
2012-06-25 19:59 ` Doug Evans
2012-06-26 13:31 ` Mark Kettenis
2012-06-26 13:15 ` Mark Kettenis
2012-06-26 11:51 ` Mark Kettenis
2012-05-23 7:10 ` Andreas Schwab
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=4FBD01B0.5050108@redhat.com \
--to=palves@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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