From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: New ARI warning Wed May 23 01:55:03 UTC 2012
Date: Wed, 23 May 2012 07:27:00 -0000 [thread overview]
Message-ID: <CADPb22QOSCV240MV2m0KmsXfNb9O5_WsA+7Jsjn1UJwigaNTrQ@mail.gmail.com> (raw)
In-Reply-To: <CADPb22QBYSRjoqrgX7p0d5KdAZ+kEk4Ga2YrfHMrm_t_yKCE6w@mail.gmail.com>
Hmmm, there's more than a few uses of long long in gdb (not all
conditioned on CC_HAS_LONG_LONG, though most are in target files) and
gdbserver (I was pretty sure I checked at the time).
So is this ARI check outdated?
I'm happy to change the code as necessary.
If we can't use C++ can we at least use a modern C? 1/2 :-)
On Wed, May 23, 2012 at 12:10 AM, Doug Evans <dje@google.com> wrote:
> Well, blech.
> src/include/leb128.h uses long long per request, so that's what I used here.
> src/include/anything obviously cannot use LONGEST/ULONGEST.
>
> Are long long's really verboten?
>
> I suppose I could create a gdb-leb128.h that used LONGEST/ULONGEST,
> but blech.
>
>
> On Tue, May 22, 2012 at 9:17 PM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> WDYT about the following patch? I would like you to take a look at the
>> gdb/dwarf2expr.h's castings that I had to make in order to get the
>> compilation right.
next prev parent reply other threads:[~2012-05-23 7: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 ` Andreas Schwab
2012-05-23 7:10 ` Doug Evans
2012-05-23 7:27 ` Doug Evans [this message]
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
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
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=CADPb22QOSCV240MV2m0KmsXfNb9O5_WsA+7Jsjn1UJwigaNTrQ@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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