[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] IOMMU/x86: fix build with old gcc after IO-APIC RTE changes


  • To: Julien Grall <julien@xxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Thu, 17 Aug 2023 09:25:56 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=CyDc78t3Wi3bKP0WICtCTdLDXetl0D57ArMRu7OsZew=; b=PfBsEhGHPBI7EQGAdmZeEqolkBXqk+xPC4PbtnGl+Nv9MBFCq7EQd4GQXSRQveM3KbC80zroZugU3RSS3qIQpKgUgX3EsPlMPSTmlmghdDA7pRrkuRxI9xacskEL91SVREUuQKScG9tOxiR7AZM3mGM5z5tEkoCUaY1d5c/7sByWS1KA6LSWF/rM2FRvrr+GJvkPdxy8rtnrjggJM83M4rXWTGfxxiG/Zzx2Y2afjNyQsHTO/sLh7YzFKuJA/+0c/q0za2uXNrXQD5eu4QPVIPZBwu3gzN2bJGY2rGjKSVGFow9gjg8xGPaYWTUYU9Ew44VnI+c5GkLYGNdoRY0C7Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Wa1UOBVLXNuu1lGYMZnBpSrgQJg9vb1nQGB44w7xyWTK5BHTJiaIy+xICwsJREzalDLfn0G3GnG5iY1jEBMe5fD3QPYta3BWmUNnGrsZwZCQQuYGSugPBSk2Y13lL9VNzEevFVXRAuynX86armZkGsnustMEO4KdMx2dvs+qvCYoVK+21UwOsDnc7SOek13RDxfDikhEQ+QKwaBJiRhYGVpNbHFYYd93OZsgcXXepst7+cVqslQTAUbq9gulHhQlMN4vqTNMneIL3njcQfYJunM64TyJJfHlUbfT/Qn/UoItHTwqqlStga4NIoNcNQ68wN8MTbahbGw+nbt3xJ5LDg==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 17 Aug 2023 07:26:19 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 17.08.2023 09:06, Julien Grall wrote:
> On 17/08/2023 07:39, Jan Beulich wrote:
>> On 16.08.2023 18:57, Julien Grall wrote:
>>> On 16/08/2023 10:51, Jan Beulich wrote:
>>>> Old gcc won't cope with initializers involving unnamed struct/union
>>>
>>> Can you specify the newest version of GCC that breaks? This would help
>>> to reproduce your problem in case someone complain about this change.
>>
>> I can't, without actually putting in effort to find out. I'm observing
>> these problems with 4.3.x iirc.
> 
> You are proving my point. :) If you can't already remember which version 
> of GCC was breaking. How can you expect someone in a few months time to 
> figure out why this was added and whether and it can reworked differently?

Well, I know for sure that this doesn't work with the version recorded in
./README. Imo that's sufficient to justify submitting patches like this,
and without going into version details. Once that baseline version is
bumped, much more than just this code can and wants to be re-evaluated,
by simply trying with the then-lowest supported version (which imo really
ought to be part of what is tested in CI, to not always leave it to me to
find and fix such issues).

>>  And of course this isn't the first such
>> change, and I don't think we ever bothered writing down precise version
>> boundaries in any of the commits.
> 
> I am not looking at a precise boundary. What I meant by the 'newest' is 
> the newest one you try.

Okay, that's slightly different and hence possible to record. I can do
so here just to please you, but as per above I don't think that ought to
be a requirement (and as said earlier it also hasn't been in the past).

> With 'old', it is not clear what this really mean. For instance, 
> technically the previous GCC version is already old. So a bit more 
> information about the GCC version you tried on would be useful.

Hmm, no, that's not really my interpretation of "old".

Jan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.