public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3] Use strtoll instead of atoll in gcov-tool.c
Date: Thu, 08 Jan 2015 12:27:00 -0000	[thread overview]
Message-ID: <CAFiYyc0Qg1SHbz_g44Hio9N7YD45VELoSM_W3OOcbQNKfPMWVg@mail.gmail.com> (raw)
In-Reply-To: <BLU437-SMTP391D2867A5E9CF3834011B97680@phx.gbl>

On Sat, Dec 20, 2014 at 11:51 PM, John David Anglin
<dave.anglin@bell.net> wrote:
> Ping.

Ok.

Thanks,
Richard.

>
> On 24-Nov-14, at 7:38 PM, John David Anglin wrote:
>
>> On 15-Sep-14, at 5:40 AM, Richard Biener wrote:
>>
>>> Let's wait for other opinions.
>>
>>
>> We now have implementations of strtol and strtoll in libiberty.  So, it's
>> better to use
>> these than atoll.  As suggested by Jakub, the patch now falls back to
>> int64_t if the
>> host doesn't have long long.
>>
>> Tested on hppa2.0w-hpux11.11 and hppa64-hp-hpux11.11.
>>
>> Okay for trunk?
>>
>> Dave
>> --
>> John David Anglin       dave.anglin@bell.net
>>
>>
>> <gcov-tool.c.d.3>
>
>
>
> Dave
> --
> John David Anglin       dave.anglin@bell.net
>
>
>

      reply	other threads:[~2015-01-08 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-07 17:36 [PATCH] Use sscanf " John David Anglin
2014-09-08  9:21 ` Richard Biener
2014-09-14 19:05   ` [PATCH v2] " John David Anglin
2014-09-15 10:38     ` Richard Biener
2014-11-25  1:36       ` [PATCH v3] Use strtoll " John David Anglin
2014-12-20 23:41         ` John David Anglin
2015-01-08 12:27           ` Richard Biener [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=CAFiYyc0Qg1SHbz_g44Hio9N7YD45VELoSM_W3OOcbQNKfPMWVg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=dave.anglin@bell.net \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).