From: Patrick Robb <probb@iol.unh.edu>
To: Doug Foster <Doug.Foster@arm.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, dev <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>,
Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Subject: Re: meson error on ARM Grace server 23.11/22.11
Date: Tue, 20 May 2025 13:15:27 -0400 [thread overview]
Message-ID: <CAJvnSUA9YPmxv_7RF6=zoM-LKPGTRy1Eppswf9qds1BcojpZ9Q@mail.gmail.com> (raw)
In-Reply-To: <AS8PR08MB733911AE8B83C45AFF3632BFE59FA@AS8PR08MB7339.eurprd08.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3733 bytes --]
Hi Doug,
Without overburdening you with details, at the CI lab we have some tests
which run with werror=true (treat warnings as errors) and some which run
without it. The tests which I'm currently trying to extend to LTS for Grace
do not have this flag included, i.e. they are tolerant to warnings. So, we
should be good to proceed with your patch.
Although no warnings on 22.11 and 23.11 would open us up to adding
werror=true build tests directly on Grace in the future, there isn't an ask
for this right now and I don't think we will need to support it. So, again
I think we can proceed with your patch as is.
Thanks for handling this.
On Tue, May 20, 2025 at 1:00 PM Doug Foster <Doug.Foster@arm.com> wrote:
> Hi Patrick,
>
> While building 22.11 and 23.11 with GCC 13.3, I noticed compiler warnings
> related to memcpy usage, specifically involving __builtin___memcpy_chk
> failures.
> Would these warnings be a concern for CI test runs, or are they generally
> tolerated?
>
> From: Doug Foster
> Sent: Friday, May 16, 2025 12:16 AM
> To: Patrick Robb <probb@iol.unh.edu>; Wathsala Wathawana Vithanage <
> wathsala.vithanage@arm.com>
> Cc: ci@dpdk.org; dev <dev@dpdk.org>; Honnappa Nagarahalli <
> Honnappa.Nagarahalli@arm.com>; stable@dpdk.org; nd <nd@arm.com>
> Subject: RE: meson error on ARM Grace server 23.11/22.11
>
> Hi Patrick,
>
> I will produce the patches with necessary changes to build on Grace for
> 22.11 and 23.11.
>
> From: Patrick Robb <mailto:probb@iol.unh.edu>
> Sent: Thursday, May 15, 2025 3:59 PM
> To: Wathsala Wathawana Vithanage <mailto:wathsala.vithanage@arm.com>
> Cc: mailto:ci@dpdk.org; dev <mailto:dev@dpdk.org>; Honnappa Nagarahalli
> <mailto:Honnappa.Nagarahalli@arm.com>; mailto:stable@dpdk.org; Doug
> Foster <mailto:Doug.Foster@arm.com>; nd <mailto:nd@arm.com>
> Subject: Re: meson error on ARM Grace server 23.11/22.11
>
> Thanks Wathsala,
>
> How can we help on the UNH side? Do you want us to produce the 22.11 and
> 23.11 diffs/patches, which would be based on d007038, with some
> modifications based on what you had said to Doug?
>
> I'm not sure what the process looks like exactly for providing backports
> to LTS maintainers.
>
> On Tue, Apr 29, 2025 at 12:00 PM Wathsala Wathawana Vithanage <mailto:
> wathsala.vithanage@arm.com> wrote:
> > Hi,
> >
> > At the DPDK Community Lab we have been running CI tests with a new ARM
> > Grace server for the past couple of months on main and next-* branches.
> I am
> > trying to add LTS runs now, and ran into a snag with 23.11 and 22.11 for
> this
> > system. Stable maintainers I'm not sure whether this should be addressed
> or not
> > for hardware which is new and didn't exist when 22.11 and 23.11 were
> > released... but I figured I'd make the tickets and find out. I attached
> the meson
> > logs to the tickets and if for whatever reason you guys want to remote
> into this
> > machine, I'm happy to setup the VPN and SSH access.
> >
> > 22.11: https://bugs.dpdk.org/show_bug.cgi?id=1703
> > 23.11: https://bugs.dpdk.org/show_bug.cgi?id=1702
>
> +doug
>
> neoverse-v2 is supported in the GCC 13.3 used for this build although
> -mtune/-mcpu
> for grace is not available in that version.
> Adding neoverse-v2 and soc_grace with crypto extension should bring these
> releases
> on par with latest.
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
[-- Attachment #2: Type: text/html, Size: 5336 bytes --]
prev parent reply other threads:[~2025-05-20 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:43 Patrick Robb
2025-04-29 8:30 ` Kevin Traynor
2025-04-29 11:03 ` Luca Boccassi
2025-04-29 15:59 ` Wathsala Wathawana Vithanage
2025-05-15 20:59 ` Patrick Robb
2025-05-16 5:16 ` Doug Foster
2025-05-20 16:59 ` Doug Foster
2025-05-20 17:15 ` Patrick Robb [this message]
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='CAJvnSUA9YPmxv_7RF6=zoM-LKPGTRy1Eppswf9qds1BcojpZ9Q@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Doug.Foster@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=wathsala.vithanage@arm.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 NNTP newsgroup(s).