All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, Julien Grall <jgrall@amazon.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Ian Jackson <iwj@xenproject.org>, Jan Beulich <jbeulich@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH for-4.15] xen: Bump the minimum version of GCC supported to 4.9 (5.1 on arm64)
Date: Sun, 7 Mar 2021 12:37:21 +0000	[thread overview]
Message-ID: <6d312453-a949-143b-f4a6-e7fac7ef6486@xen.org> (raw)
In-Reply-To: <YESxpOByQ+7gXeI0@Air-de-Roger>

Hi Roger,

On 07/03/2021 10:57, Roger Pau Monné wrote:
> On Sat, Mar 06, 2021 at 09:41:48PM +0000, Julien Grall wrote:
>> From: Julien Grall <jgrall@amazon.com>
>>
>> Compilers older than 4.8 have known codegen issues which can lead to
>> silent miscompilation:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58145
>>
>> Furthermore, pre-4.9 GCC have known bugs (including things like
>> internal compiler errors on Arm) which would require workaround (I
>> haven't checked if we have any in Xen).
>>
>> The minimum version of GCC to build the hypervisor is now raised to 4.9.
> 
> The README entry doesn't differentiate between tools and hypervisor
> GCC version, can the bug above also manifest in toolstack code?

I guess it can manifest in the firmware (e.g. hvmloader, rombios). It 
looks rather unlikely in the userspace tools as we seem to barely use 
volatile.

For the Arm64 bug [1], I think it can also show up when receiving a signal.

> 
> I don't think it makes much sense to have diverging requirements for
> tools vs hypervisor builds, but if the bug(s) can also manifest in
> toolstack code we might want to add a GCC version check to
> tools/configure.ac.

Agree. I can add check in ./configure for the toolstack.

Cheers,

[1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63293

-- 
Julien Grall


  reply	other threads:[~2021-03-07 12:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-06 21:41 [PATCH for-4.15] xen: Bump the minimum version of GCC supported to 4.9 (5.1 on arm64) Julien Grall
2021-03-07 10:57 ` Roger Pau Monné
2021-03-07 12:37   ` Julien Grall [this message]
2021-03-08  8:09 ` Jan Beulich
2021-03-08 10:51   ` Julien Grall
2021-03-08 11:20     ` Jan Beulich
2021-03-08 20:22       ` Julien Grall
2021-03-09 11:20         ` Jan Beulich
2021-03-10 18:05           ` Julien Grall
2021-03-11  8:17             ` Jan Beulich
2021-03-11  9:31               ` Julien Grall
2021-03-11 11:43                 ` Jan Beulich
2021-03-08  9:49 ` Ian Jackson
2021-03-10 20:48 ` Stefano Stabellini
     [not found] <161507188317.11025.6744028462008264481@c667a6b167f6>
2021-03-07 13:00 ` Julien Grall
2021-03-09  0:59   ` Stefano Stabellini
2021-03-09 10:05     ` Julien Grall
2021-03-09 10:32       ` Roger Pau Monné
2021-03-09 11:11         ` Anthony PERARD
2021-03-09 22:24         ` Stefano Stabellini
2021-03-10  7:52           ` Roger Pau Monné
2021-03-10 10:24             ` Zheng, Fam

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=6d312453-a949-143b-f4a6-e7fac7ef6486@xen.org \
    --to=julien@xen.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@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.