From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, rkrcmar@redhat.com
Subject: Re: [kvm-unit-tests PATCH 2/4] lib/alloc: fix format warnings, add/use PRIx64
Date: Tue, 1 Mar 2016 12:04:01 +0100 [thread overview]
Message-ID: <56D57721.7050807@redhat.com> (raw)
In-Reply-To: <20160301091539.e5l2uec4iv6kfsn5@hawk.localdomain>
On 01/03/2016 10:15, Andrew Jones wrote:
>> > So libcflat uses the header stdint.h from the standard gcc installation
>> > to get the uint64_t and friends, but you define the PRIx64 etc. here
>> > manually? That sounds strange... You could simply include "inttypes.h"
>> > instead of "stdint.h" in this libcflat.h header file, then you would get
>> > PRIx64 and friends automatically instead.
> We can only include headers that are provided by libgcc in arch-neutral
> files like libcflat, in order for cross-compiling to work. inttypes.h
> isn't available.
Yup, inttypes.h is not part of the freestanding environment.
> > OTOH, for a stand-alone binary like kvm-unit-tests, it's also somewhat
> > risky to compile without "-nostdinc" since unwanted headers might be
> > included that way (e.g. what happens if someone writes "#include
> > <stdio.h>" by accident? You likely get some nice confusion...). So maybe
> > it would be better to compile with "-nostdinc" instead and define all
> > necessary things manually here?
>
> We don't have -nostdinc because sometimes the x86 tests cheat and use
> standard includes. arm and powerpc Makefiles could/should add it though,
> as they don't currently cheat, and it's probably best if they never do.
Some of the includes are part of the freestanding environment: float.h,
iso646.h, limits.h, stdarg.h, stdbool.h, stddef.h, stdint.h and probably
a few more in C11 (e.g. stdalign.h, stdatomic.h, stdnoreturn.h). Using
them is not cheating.
Paolo
next prev parent reply other threads:[~2016-03-01 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 20:19 [kvm-unit-tests PATCH 0/4] add fmt warnings to printf, and fix bad uses Andrew Jones
2016-02-29 20:19 ` [kvm-unit-tests PATCH 1/4] lib: *printf: warn on format/arg mismatch Andrew Jones
2016-03-01 10:43 ` Paolo Bonzini
2016-03-01 11:01 ` Andrew Jones
2016-02-29 20:19 ` [kvm-unit-tests PATCH 2/4] lib/alloc: fix format warnings, add/use PRIx64 Andrew Jones
2016-03-01 4:58 ` Thomas Huth
2016-03-01 9:15 ` Andrew Jones
2016-03-01 11:04 ` Paolo Bonzini [this message]
2016-03-01 12:22 ` Andrew Jones
2016-03-01 10:47 ` Paolo Bonzini
2016-02-29 20:19 ` [kvm-unit-tests PATCH 3/4] arm64: fix printf format warnings Andrew Jones
2016-03-01 5:01 ` Thomas Huth
2016-03-01 9:17 ` Andrew Jones
2016-02-29 20:19 ` [kvm-unit-tests PATCH 4/4] x86: " Andrew Jones
2016-03-01 5:30 ` Thomas Huth
2016-03-01 9:24 ` Andrew Jones
2016-03-01 10:52 ` Paolo Bonzini
2016-03-01 11:02 ` Andrew Jones
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=56D57721.7050807@redhat.com \
--to=pbonzini@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.