From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120])
 by mx.groups.io with SMTP id smtpd.web12.539.1590092585977755312
 for <devel@edk2.groups.io>;
 Thu, 21 May 2020 13:23:06 -0700
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PSENyhhl;
 spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1590092585;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=oNgYJXhPPxMcVFK2kuM2oSKkLac4ti2DLPx7YfKiAxU=;
	b=PSENyhhlH+jWZAN0qnEiqkkVLvAuV+z6d8SU3SaW4SSRh/16DEroAeOKVKFWoxGBApaCyr
	SJ506MaUKap9NjuznpPCvhr0XmY6fBubBZ/lAJOvWUrumoMsbWlRi7UiuaToJ11O06TBEU
	aysqNcgTphk4Rk2yK7IT+mF/9mK8E7Q=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-333-iKGAN02lP-WnI7wQEnSr-w-1; Thu, 21 May 2020 16:23:01 -0400
X-MC-Unique: iKGAN02lP-WnI7wQEnSr-w-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 333AC8015D2;
	Thu, 21 May 2020 20:23:00 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-113-225.ams2.redhat.com [10.36.113.225])
	by smtp.corp.redhat.com (Postfix) with ESMTP id F172183841;
	Thu, 21 May 2020 20:22:58 +0000 (UTC)
Subject: Re: [edk2-devel] [PATCH v2] ArmPkg/CompilerIntrinsicsLib: provide atomics intrinsics
To: Leif Lindholm <leif@nuviainc.com>, devel@edk2.groups.io,
 ard.biesheuvel@arm.com
Cc: glin@suse.com, liming.gao@intel.com
References: <20200520114448.26104-1-ard.biesheuvel@arm.com>
 <20200521112353.GS1923@vanye> <de3d4703-f374-c0d6-e871-76b9f45d9753@arm.com>
 <20200521131644.GT1923@vanye> <059e1db5-8228-63a8-09ab-bb0efcd95176@arm.com>
 <20200521141615.GU1923@vanye>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <036f7682-0903-40aa-3743-6a383b742b88@redhat.com>
Date: Thu, 21 May 2020 22:22:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20200521141615.GU1923@vanye>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Language: en-US
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 05/21/20 16:16, Leif Lindholm wrote:

> OK, then I would vote *for* merging the patch regardless. We know how
> long some toolchain versions can stick around simply because they were
> mentioned in some blog post somewhere that ended up high in search
> rankings.
> 
> Once gcc 10.2 is released (and we have verified the problem can be
> worked around elsewhere), I guess we could add a note saying "once all
> gcc 10.0 and 10.1 toolchains are considered obsolete, this file can
> be deleted".

I think we can expect all distros that ship gcc-10 to eventually migrate
to gcc-10.2+. Until then, this patch should hopefully work. (I'm quite
annoyed by having to call the patch "temporary", as it feels very
technically impressive.)

So I think I agree with Leif, with a small modification to the idea:
rather than a *note* saying "back this out once 10.0 and 10.1 have been
replaced by 10.2+ in all 'large' distros", I would suggest filing a *BZ*
for the same. And I recommend making the new BZ dependent on
TianoCore#2723 (i.e. the present BZ).

Thanks!
Laszlo