From: Andrii Anisov <andrii.anisov@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Julien Grall <julien@xen.org>,
xen-devel@lists.xenproject.org,
Andrii Anisov <andrii_anisov@epam.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [RFC 7/7] arm/gic-v3: add GIC version suffix to iomem range variables
Date: Thu, 14 Nov 2019 10:35:47 +0200 [thread overview]
Message-ID: <3884e2f3-b523-01ac-e3c3-d6229a91d703@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1911111258060.2677@sstabellini-ThinkPad-T480s>
Hello Stefano,
On 11.11.19 22:59, Stefano Stabellini wrote:
> this seems a very serious compiler bug.
Yep.
> This, together with the other bug described in the previous patch, makes
> me think the ARMCC is not quite ready for showtime.
Yet, this particular ARM Compiler version is safety certified and LTS.
> Do you know if there
> are any later version of the compiler that don't have these problems?
I don't know, ARM did not say something special about it. As I know, the reason to take this compiler version was that it is the "latest and greatest" safety certified
> I would hate to introduce these workarounds
I hated finding and publishing these workarounds, but here we are.
The main question here is if XEN needs a tag "Support safety certified compiler" by the cost of accepting such workarounds.
Then discuss how to reduce their stench.
--
Sincerely,
Andrii Anisov.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-11-14 8:36 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 9:19 [Xen-devel] [RFC 0/7] Build XEN with ARM Compiler 6.6.3 Andrii Anisov
2019-11-06 9:19 ` [Xen-devel] [RFC 1/7] xen: clang: Support correctly cross-compile Andrii Anisov
2019-11-06 11:07 ` Wei Liu
2019-11-06 15:24 ` Jan Beulich
2019-11-18 6:08 ` Julien Grall
2019-11-06 9:19 ` [Xen-devel] [RFC 2/7] WIP: Compilation with ARM DS-6 compiler Andrii Anisov
2019-11-06 15:28 ` Jan Beulich
2019-11-06 22:08 ` Artem Mygaiev
2019-11-07 7:31 ` Jan Beulich
2019-11-13 17:15 ` Artem Mygaiev
2019-11-13 23:19 ` Julien Grall
2019-11-14 14:12 ` Artem Mygaiev
2019-11-18 6:18 ` Julien Grall
2019-11-19 15:16 ` Artem Mygaiev
2019-11-19 16:13 ` Julien Grall
2019-11-06 9:19 ` [Xen-devel] [RFC 3/7] arm64:armds: ARM Compiler 6.6 does not accept `rx` registers naming for AArch64 Andrii Anisov
2019-11-06 15:32 ` Jan Beulich
2019-11-11 20:49 ` Stefano Stabellini
2019-11-13 5:56 ` Julien Grall
2019-11-06 9:19 ` [Xen-devel] [RFC 4/7] arm/gic: Drop pointless assertions Andrii Anisov
2019-11-11 20:52 ` Stefano Stabellini
2019-11-13 1:14 ` Julien Grall
2019-11-20 22:15 ` Stefano Stabellini
2019-11-06 9:19 ` [Xen-devel] [RFC 5/7] WIP:arm64:armds: Build XEN with ARM Compiler 6.6 Andrii Anisov
2019-11-11 21:26 ` Stefano Stabellini
2019-11-13 5:50 ` Julien Grall
2019-11-14 11:31 ` Andrii Anisov
2019-11-18 7:03 ` Julien Grall
2019-11-14 11:14 ` Andrii Anisov
2019-11-20 22:56 ` Stefano Stabellini
2019-11-06 9:19 ` [Xen-devel] [RFC 6/7] arm: Introduce dummy empty functions for data only C files Andrii Anisov
2019-11-11 20:57 ` Stefano Stabellini
2019-11-13 16:41 ` Andrii Anisov
2019-11-13 23:03 ` Julien Grall
2019-11-14 13:32 ` Artem Mygaiev
2019-11-20 22:20 ` Stefano Stabellini
2019-11-13 5:51 ` Julien Grall
2019-11-13 17:07 ` Andrii Anisov
2019-11-06 9:19 ` [Xen-devel] [RFC 7/7] arm/gic-v3: add GIC version suffix to iomem range variables Andrii Anisov
2019-11-11 20:59 ` Stefano Stabellini
2019-11-13 1:25 ` Julien Grall
2019-11-14 8:35 ` Andrii Anisov [this message]
2019-11-20 22:23 ` Stefano Stabellini
2019-11-21 9:05 ` Andrii Anisov
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=3884e2f3-b523-01ac-e3c3-d6229a91d703@gmail.com \
--to=andrii.anisov@gmail.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrii_anisov@epam.com \
--cc=julien@xen.org \
--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 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.