xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	nd@arm.com, Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 3/3] arm: fix build with gcc 7
Date: Fri, 19 May 2017 08:48:58 +0100	[thread overview]
Message-ID: <e728780d-7b0a-f158-edc2-dfaec60bbfbf@arm.com> (raw)
In-Reply-To: <591EA9E4020000780015B2A5@prv-mh.provo.novell.com>

Hi Jan,

On 19/05/2017 07:16, Jan Beulich wrote:
>>>> On 18.05.17 at 17:12, <julien.grall@arm.com> wrote:
>> On 18/05/17 09:41, Jan Beulich wrote:
>>> The compiler dislikes duplicat "const", and the ones it complains about
>>
>> s/duplicat/duplicate/
>>
>>> look like they we in fact meant to be placed differently.
>>>
>>> Also fix array_access_okay() (just like on x86), despite the construct
>>> being unused on ARM: -Wint-in-bool-context, enabled by default in
>>> gcc 7, doesn't like multiplication in conditional operators. "Hide" it,
>>> at the risk of the next compiler version becoming smarter and
>>> recognizing even that. (The hope is that added smartness then would
>>> also better deal with legitimate cases like the one here.) The change
>>> could have been done in access_ok(), but I think we better keep it at
>>> the place the compiler is actually unhappy about.
>>
>> I am wondering if we should drop array_access_ok and access_ok as they
>> are not used.
>
> I did consider this too, but thought that such a decision (and patch)
> would better come from someone closer to ARM.

I will send a patch for this patch after 4.9.

Cheers,

>
>> Anyway, I am happy with both way:
>>
>> Reviewed-by: Julien Grall <julien.grall@arm.com>
>
> Thanks, Jan
>

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-05-19  7:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  8:01 [PATCH 0/3] gcc 7 build fixes (hypervisor side) Jan Beulich
2017-05-18  8:34 ` Julien Grall
2017-05-18  8:42   ` Jan Beulich
2017-05-18  8:39 ` [PATCH 1/3] xmalloc: correct _xmalloc_array() indentation Jan Beulich
2017-05-18  9:40   ` Wei Liu
2017-05-18 10:16     ` Andrew Cooper
2017-05-18  8:40 ` [PATCH 2/3] x86: fix build with gcc 7 Jan Beulich
2017-05-18 10:18   ` Andrew Cooper
2017-05-18  8:41 ` [PATCH 3/3] arm: " Jan Beulich
2017-05-18 15:12   ` Julien Grall
2017-05-18 18:35     ` Stefano Stabellini
2017-05-19  6:45       ` Jan Beulich
2017-05-19  6:16     ` Jan Beulich
2017-05-19  7:48       ` Julien Grall [this message]
2017-05-18 15:14 ` [PATCH 0/3] gcc 7 build fixes (hypervisor side) Julien Grall

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=e728780d-7b0a-f158-edc2-dfaec60bbfbf@arm.com \
    --to=julien.grall@arm.com \
    --cc=JBeulich@suse.com \
    --cc=nd@arm.com \
    --cc=sstabellini@kernel.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 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 NNTP newsgroup(s).