From: Chris Paterson <Chris.Paterson2@renesas.com>
To: Denys Fedoryshchenko <denys.f@collabora.com>,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
clang-built-linux <llvm@lists.linux.dev>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: RE: Migration to Debian Bookworm and compiler updates for KernelCI
Date: Tue, 12 Mar 2024 16:13:25 +0000 [thread overview]
Message-ID: <TYWPR01MB11862CF20936D7CD75B2BDF87B72B2@TYWPR01MB11862.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <42c7f5a3e07c274c2a9d2e45a973c6306b2ba74f.camel@collabora.com>
+ CIP people
(sorry for the delay)
> From: Denys Fedoryshchenko <denys.f@collabora.com>
> Sent: Thursday, March 7, 2024 11:02 AM
>
> Hello,
>
> I'm reaching out on behalf of the KernelCI project team to discuss our
> current compiler setup and planned migration to Debian Bookworm.
>
> As you may know, our compiler images are currently based on Debian
> Bullseye, which is approaching its end of life in July 2024. We have
> been testing using gcc-10, which has presented us with some recent
> challenges, notably a significant bug that results in false positive
> compilation errors (specifically, the -Werror memcpy issue in
> security.c). This situation has prompted us to consider an urgent
> migration to Debian Bookworm. Additionally, the migration is
> necessitated by our requirement to upgrade to a newer Python version to
> support KernelCI v2 development efforts.
>
> However, before we proceed, we have a couple of pending questions that
> we hope to get clarity on:
>
> 1) We've noticed that the minimal available version of clang on
> https://apt.llvm.org/bookworm/dists/ is 15, whereas our current minimal
> requirement for the Linux kernel compilation is clang-13.0.1
> (https://www.kernel.org/doc/html/next/process/changes.html). How
> critical is it to continue providing compile tests for clang-13 (and
> potentially clang-14)? This information would be vital for us in
> planning our compiler support strategy moving forward.
>
> 2) We are also considering migrating to gcc-12 and would like to
> inquire if the CIP (Civil Infrastructure Platform) could provide their
> endorsement for this move. Should there be any reservations about
> transitioning to gcc-12, we would greatly appreciate development
> support in building gcc-10 for Bookworm. In the interim, we would like
> to inquire if it's acceptable to continue using our current gcc-10
> images based on Bullseye until such a migration is feasible.
Jan, Iwamatsu-san, Arisu-san,
Do you have any comments here?
Thanks, Chris
>
> We believe that addressing these questions is crucial for our project's
> progression and ensuring that we maintain a robust and reliable build
> environment for the Linux kernel. We eagerly await your feedback and
> any recommendations you may have regarding our migration plan and
> compiler version support.
>
> Thank you for your time and consideration.
>
> Best regards,
>
> Denys Fedoryshchenko
next parent reply other threads:[~2024-03-12 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42c7f5a3e07c274c2a9d2e45a973c6306b2ba74f.camel@collabora.com>
2024-03-12 16:13 ` Chris Paterson [this message]
2024-03-12 16:44 ` Migration to Debian Bookworm and compiler updates for KernelCI Jan Kiszka
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=TYWPR01MB11862CF20936D7CD75B2BDF87B72B2@TYWPR01MB11862.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
--cc=denys.f@collabora.com \
--cc=iwamatsu@nigauri.org \
--cc=jan.kiszka@siemens.com \
--cc=kernelci@lists.linux.dev \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@google.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).