From: Ian Lance Taylor <iant@google.com>
To: dje@google.com (Doug Evans)
Cc: gcc-patches@sourcware.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: [RFA] leb128.h: Umm, how about int64_t?
Date: Wed, 23 May 2012 18:31:00 -0000 [thread overview]
Message-ID: <mcr396qvjfi.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <20120523164123.099BD2461B1@ruffy.mtv.corp.google.com> (Doug Evans's message of "Wed, 23 May 2012 09:41:22 -0700 (PDT)")
dje@google.com (Doug Evans) writes:
> 2012-05-23 Doug Evans <dje@google.com>
>
> * leb128.h: #include stdint.h, inttypes.h.
> (read_uleb128_to_uint64): Renamed from read_uleb128_to_ull.
> Change to take a uint64_t * argument instead of unsigned long long.
> (read_sleb128_to_uint64): Renamed from read_sleb128_to_ll.
> Change to take an int64_t * argument instead of long long.
This is OK.
Thanks.
Ian
prev parent reply other threads:[~2012-05-23 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 16:41 Doug Evans
2012-05-23 18:31 ` Ian Lance Taylor [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=mcr396qvjfi.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=dje@google.com \
--cc=gcc-patches@sourcware.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