From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Doug Goldstein <cardoe@cardoe.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/2] README: bump minimum required clang/llvm version
Date: Thu, 29 Feb 2024 15:21:04 +0100 [thread overview]
Message-ID: <ZeCS0OC4FsbEXo8S@macbook> (raw)
In-Reply-To: <132dde96-d7d3-4823-8a0e-7b4a62526f2e@suse.com>
On Thu, Feb 29, 2024 at 02:12:26PM +0100, Jan Beulich wrote:
> On 29.02.2024 14:01, Jan Beulich wrote:
> > On 29.02.2024 13:40, Roger Pau Monné wrote:
> >> On Thu, Feb 29, 2024 at 01:11:55PM +0100, Jan Beulich wrote:
> >>> On 29.02.2024 10:55, Roger Pau Monne wrote:
> >>>> --- a/README
> >>>> +++ b/README
> >>>> @@ -41,7 +41,7 @@ provided by your OS distributor:
> >>>> - GCC 4.1.2_20070115 or later
> >>>> - GNU Binutils 2.16.91.0.5 or later
> >>>> or
> >>>> - - Clang/LLVM 3.5 or later
> >>>> + - Clang/LLVM 14.0.0 or later
> >>>
> >>> Wow, that's a big step. I'm build-testing with Clang7 on one system and
> >>> with Clang5 on another (and the latter more frequently than the former).
> >>> If any real dependency on this new a version (about 3 years old?) was
> >>> introduced, I would then no longer be able to locally test any Clang
> >>> builds (and hence the risk would again increase that I introduce issues
> >>> that affect just Clang builds).
> >>
> >> Would it be possible for you to update to a newer version? I see both
> >> the OpenSUSE containers in Gitlab have newer versions of Clang.
> >
> > No. These are SLES versions which I'm not intending to touch. See
> >
> > https://lists.xen.org/archives/html/xen-devel/2024-02/msg01793.html
> >
> > and
> >
> > https://lists.xen.org/archives/html/xen-devel/2024-02/msg01795.html
> >
> > for why. The most recent piece of hardware I've installed a fresh (but
> > not exactly new, yet still fully supported) SLES version on would
> > apparently offer Clang7 only, either.
Hm, OK. Would containers be an option?
I don't know for gcc, but for clang I'm quite sure the only run time
tested builds are the ones used by FreeBSD. I'm hesitant to claim
clang versions as supported when they are only tested to generate an
output without triggering any errors, but there's no testing at all
that the generated code is functional.
> Bah, that's not even Clang, only LLVM.
I'm confused by this, doesn't your llvm package include clang?
Thanks, Roger.
next prev parent reply other threads:[~2024-02-29 14:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 9:55 [PATCH 0/2] Restrict Clang/LLVM supported versions Roger Pau Monne
2024-02-29 9:55 ` [PATCH 1/2] README: bump minimum required clang/llvm version Roger Pau Monne
2024-02-29 12:11 ` Jan Beulich
2024-02-29 12:40 ` Roger Pau Monné
2024-02-29 13:01 ` Jan Beulich
2024-02-29 13:12 ` Jan Beulich
2024-02-29 14:21 ` Roger Pau Monné [this message]
2024-02-29 14:28 ` Jan Beulich
2024-03-12 22:45 ` Julien Grall
2024-02-29 9:55 ` [PATCH 2/2] automation: introduce non debug clang based tests Roger Pau Monne
2024-03-05 17:29 ` Roger Pau Monné
2024-03-07 22:15 ` Stefano Stabellini
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=ZeCS0OC4FsbEXo8S@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--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.