public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] ari, btrace: avoid unsigned long long
Date: Wed, 08 Jul 2015 13:40:00 -0000	[thread overview]
Message-ID: <559D2855.9010501@redhat.com> (raw)
In-Reply-To: <1436360074-8625-3-git-send-email-markus.t.metzger@intel.com>

On 07/08/2015 01:54 PM, Markus Metzger wrote:
> Fix the ARI warning about the use of unsigned long long.  We can't use ULONGEST
> as this is defined unsigned long on 32-bit systems.

Hmm, it is?

I'm looking at common/common-types.h and not seeing it.

> Use unsigned long to hold
> the buffer size inside GDB and __u64 when interfacing the kernel.
> 

Thanks,
Pedro Alves

  reply	other threads:[~2015-07-08 13:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:54 [PATCH 1/4] btrace: fix build fail with 32-bit BFD Markus Metzger
2015-07-08 12:54 ` [PATCH 3/4] ari, btrace: avoid unsigned long long Markus Metzger
2015-07-08 13:40   ` Pedro Alves [this message]
2015-07-08 14:05     ` Metzger, Markus T
2015-07-08 12:54 ` [PATCH 4/4] btrace, pt: support new packets Markus Metzger
2015-07-08 13:45   ` Pedro Alves
2015-07-08 12:54 ` [PATCH 2/4] record: set stop_pc in "record goto" command Markus Metzger
2015-07-08 13:42   ` Pedro Alves
2015-07-08 15:08     ` Metzger, Markus T
2015-07-08 15:11       ` Pedro Alves
2015-07-08 13:42 ` [PATCH 1/4] btrace: fix build fail with 32-bit BFD Pedro Alves
2015-07-13  7:39   ` Metzger, Markus T
2015-07-13  9:39     ` Pedro Alves

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=559D2855.9010501@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).