From: Richard Earnshaw <rearnsha@arm.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>,
Yufeng Zhang <Yufeng.Zhang@arm.com>
Subject: Re: C99 macros
Date: Thu, 16 Aug 2012 13:44:00 -0000 [thread overview]
Message-ID: <502CEED1.8010008@arm.com> (raw)
In-Reply-To: <201208151347.37429.vapier@gentoo.org>
On 15/08/12 18:47, Mike Frysinger wrote:
> On Wednesday 15 August 2012 13:17:53 Yufeng Zhang wrote:
>> It has been pointed out that the use of the C99 macros PRIi64 and
>> PRIx64 (in opcodes/aarch64-opc.c) may cause the build to fail in
>> an environment where there is lack of C99 support.
>>
>> I am considering to eliminate the dependency on this C99 feature
>> by replacing PRIi64 and PRIx64 with some alternative approach in
>> the AArch64 port. Before doing that, I wonder what the general
>> policy is about coding the binutils using C99 features.
>> Interestingly, I didn't find any other port includes the
>> inttypes.h header file (not to say the use of PRIi64 and
>> PRIx64).
>
> we use them in gdb and the sim, although we have gnulib available
> in the gdb subdir. in general though, i don't see a problem using
> inttypes.h since glibc has had the header since 1997. wait to see
> if someone complains.
>
> also, isn't stdint.h and the uint32_t/etc... types technically C99
> ? -mike
>
Yes, though that then begs the question why, 13 years after c99 was
published, we're still restricting ourselves to a 23-year-old predecessor?
R.
next prev parent reply other threads:[~2012-08-16 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 17:47 Yufeng Zhang
2012-08-15 18:27 ` Mike Frysinger
2012-08-16 13:44 ` Richard Earnshaw [this message]
2012-08-21 19:20 ` Yufeng Zhang
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=502CEED1.8010008@arm.com \
--to=rearnsha@arm.com \
--cc=Yufeng.Zhang@arm.com \
--cc=binutils@sourceware.org \
--cc=vapier@gentoo.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).