From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
ian.campbell@citrix.com, Tim Deegan <tim@xen.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org, Wei.Liu2@citrix.com
Subject: Re: [PATCH for-4.6] xen/public: arm: Use __typeof__ rather than typeof
Date: Tue, 6 Oct 2015 18:25:03 +0100 [thread overview]
Message-ID: <561403EF.3000901@citrix.com> (raw)
In-Reply-To: <56126D8702000078000A80AC@prv-mh.provo.novell.com>
Hi Jan,
On 05/10/15 11:31, Jan Beulich wrote:
>>>> On 04.10.15 at 21:24, <julien.grall@citrix.com> wrote:
>> The keyword typeof is not portable:
>>
>> /usr/src/freebsd/sys/xen/hypervisor.h:93:2: error: implicit declaration
>> of function 'typeof' is invalid in C99
>> [-Werror,-Wimplicit-function-declaration]
>
> Actually, it's worse than that - typeof() is a gcc extension, and we
> shouldn't use extensions in public headers without at least having
> alternative code for not gcc compatible compilers in place. In fact
> we should probably aim at removing the exclusion of public/arch-%
> in the ANSI conformance check; IIRC I had to add it because things
> wouldn't build without, but with the (then forgotten) goal of dealing
> with this properly later on.
I don't see how header.chk would have catch my issue. The problem is in
the macro set_xen_guest_handle_raw which is not used within the headers
(except by set_xen_guest_handle which is not used at all).
It may be worth to add a dummy .c which call the macros to check they
are ANSI compliant.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-10-06 17:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 19:24 [PATCH for-4.6] xen/public: arm: Use __typeof__ rather than typeof Julien Grall
2015-10-05 10:31 ` Jan Beulich
2015-10-06 17:25 ` Julien Grall [this message]
2015-10-07 6:31 ` Jan Beulich
2015-10-07 8:28 ` Ian Campbell
2015-10-05 13:40 ` Wei Liu
2015-10-06 9:43 ` Julien Grall
2015-10-23 13:13 ` Julien Grall
2015-10-23 13:30 ` Ian Campbell
2015-10-23 13:52 ` Jan Beulich
2015-10-23 13:58 ` Julien Grall
2015-10-23 14:16 ` Jan Beulich
2015-10-23 14:31 ` Ian Campbell
2015-10-23 14:35 ` Ian Campbell
2015-10-23 14:37 ` Jan Beulich
2015-10-23 14:44 ` Julien Grall
2015-10-23 14:55 ` Ian Campbell
2015-10-23 15:11 ` Jan Beulich
2015-10-26 18:08 ` Julien Grall
2015-10-27 8:05 ` Jan Beulich
2015-10-28 15:44 ` Julien Grall
2015-10-28 15:52 ` Jan Beulich
2015-10-29 11:40 ` Stefano Stabellini
2015-10-27 8:07 ` Jan Beulich
2015-10-27 10:20 ` Julien Grall
2015-10-23 14:03 ` Ian Campbell
2015-10-23 14:24 ` Jan Beulich
2015-10-23 14:48 ` Ian Campbell
2015-10-23 14:55 ` Jan Beulich
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=561403EF.3000901@citrix.com \
--to=julien.grall@citrix.com \
--cc=JBeulich@suse.com \
--cc=Wei.Liu2@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 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.