This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] libctf: eschew %zi format specifier

From: Nick Alcock <nick dot alcock at oracle dot com>
To: Tom Tromey <tromey at adacore dot com>
Cc: binutils at sourceware dot org, jose dot marches at oracle dot com, tom dot tromey at adacore dot com
Date: Thu, 06 Jun 2019 12:55:29 +0100
Subject: Re: [PATCH] libctf: eschew %zi format specifier
References: <20190605123826.422222-1-nick.alcock@oracle.com> <87ftooi1ob.fsf@tromey.com> <87tvd4t11f.fsf@esperi.org.uk> <87y32fhptz.fsf@tromey.com>

On 5 Jun 2019, Tom Tromey stated:

>>>>>> "Nick" == Nick Alcock <nick.alcock@oracle.com> writes:
>
> Nick> No strndup()?! Can't we even rely on POSIX.1-2001? It's old enough to
> Nick> vote! (I guess I'll have to AC_LIBOBJ a replacement in.)
>
> libiberty has xstrndup.  Maybe there's a reason libctf can't use
> libiberty?

It is using it already (for the hashtab, for starters), and I forgot
that xstrndup existed. That makes things *much* simpler.

I'll submit a patch to switch to that shortly, as well as fixing the
other warnings you noted. :)

-- 
NULL && (void)

References:
- [PATCH] libctf: eschew %zi format specifier
  - From: Nick Alcock
- Re: [PATCH] libctf: eschew %zi format specifier
  - From: Tom Tromey
- Re: [PATCH] libctf: eschew %zi format specifier
  - From: Nick Alcock
- Re: [PATCH] libctf: eschew %zi format specifier
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]