From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id CE5BF43323;
	Tue, 14 Nov 2023 06:50:43 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 62D894027B;
	Tue, 14 Nov 2023 06:50:43 +0100 (CET)
Received: from dkmailrelay1.smartsharesystems.com
 (smartserver.smartsharesystems.com [77.243.40.215])
 by mails.dpdk.org (Postfix) with ESMTP id D380D40279
 for <dev@dpdk.org>; Tue, 14 Nov 2023 06:50:42 +0100 (CET)
Received: from smartserver.smartsharesystems.com
 (smartserver.smartsharesys.local [192.168.4.10])
 by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id AE3F6200F4;
 Tue, 14 Nov 2023 06:50:42 +0100 (CET)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PATCH v2 2/3] net/sfc: fix non-constant expression inr
 RTE_BUILD_BUG_ON()
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 14 Nov 2023 06:50:38 +0100
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F01C@smartserver.smartshare.dk>
In-Reply-To: <20231113162209.4c5fa23c@hermes.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PATCH v2 2/3] net/sfc: fix non-constant expression inr
 RTE_BUILD_BUG_ON()
Thread-Index: AdoWkJ+yMnzl5LpyTBqILD8nC2S+KgALVDeA
References: <20231111172153.57461-1-stephen@networkplumber.org>
 <20231113170605.408281-1-stephen@networkplumber.org>
 <20231113170605.408281-3-stephen@networkplumber.org>
 <20231113141326.0df15fd6@hermes.local>
 <20231113222855.GA26065@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
 <20231113161635.14f036cd@hermes.local> <20231113162209.4c5fa23c@hermes.local>
From: =?iso-8859-1?Q?Morten_Br=F8rup?= <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>,
 "Tyler Retzlaff" <roretzla@linux.microsoft.com>
Cc: <dev@dpdk.org>, <ivan.malov@oktetlabs.ru>,
 "Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
 "Ivan Malov" <ivan.malov@arknetworks.am>
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, 14 November 2023 01.22
>=20
> On Mon, 13 Nov 2023 16:16:35 -0800
> Stephen Hemminger <stephen@networkplumber.org> wrote:
>=20
> >   _Static_assert(!(0 !=3D 0), "RTE_MBUF_F_RX_IP_CKSUM_UNKNOWN !=3D =
0");
>=20
> Looks like a clang bug, or something about the other compiler flags
> because compiling just this part is fine.

Ideas:

Perhaps this file is not compiled as C11, so _Static_assert is not =
recognized. Does that part compile in the same file?
Or perhaps the C version or some compiler flags are modified (by a =
#pragma or similar) in the file.