From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f66.google.com (mail-wm1-f66.google.com [209.85.128.66]) by mx.groups.io with SMTP id smtpd.web11.10601.1590144879865741362 for ; Fri, 22 May 2020 03:54:40 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@nuviainc-com.20150623.gappssmtp.com header.s=20150623 header.b=orMf0hVY; spf=pass (domain: nuviainc.com, ip: 209.85.128.66, mailfrom: leif@nuviainc.com) Received: by mail-wm1-f66.google.com with SMTP id v19so2453391wmj.0 for ; Fri, 22 May 2020 03:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuviainc-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=bxNIZaaxYI1apdyeV52Bde88sBFMBwJbAGTtKBgaBMs=; b=orMf0hVYdY5EOq2lZ1uv+ok0ckdvhlvj9kl9oMjLClzeeXEZcG0FuLtyUZs1hY6xKW WsYJZ7kGSx+tYLMc+VeqJ+1zErjTIdhhoxS18KqS3wPIa7UGh+2ZK9r7+09h2ib54D1r HWu2ikgHpKyzFOiRbBBRYXxhK5PoPOsztR9hWWPIxRrOW+9pEjZICZKKxB+lHIg22F3o kTHxqtPROuvSFzrAxhpNxao+3L14k/Sc5sE6+mN41TW68q97yXJpUrs//BGQgi/EqoMW GdRQk4zSFVg6SE42sMcQ5bW3qQWqab9SNBTk3lbpThW2ex18LMrXiL0WTHhc7XsJKD9A vCyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=bxNIZaaxYI1apdyeV52Bde88sBFMBwJbAGTtKBgaBMs=; b=akpJyNeNgfWdGVLHBbnKApT4vx4ti2/2I1rVXGzrknXj/UWFXYf++7p99TfAbXJOgs xtUcfpXzqHjKVWn7KR3y+InIbltQuifhrtOaX8/t5x2ZjojtI6n9A3j86kJUfdkUOfb+ le5ZFFDfbO7jVYliA61u/TnM9uxENi9lwDqnstwrok4gr70Z859YiQacJm4GuL+w1oHv jJIcNm8v7n5gN2LbjSqVXrPuNnCNKqel9DpGJ6yLxfnrLSRKtoUhikDHhgK/+S7hMZY2 sFNvGSam4RFy/DMNUsbuYBUf10y5I2/0GTvuHjEn65CuIU9tZbpi3qhyAdlaOoewzTYd iTyQ== X-Gm-Message-State: AOAM533EjC6E9BFEnEWiPPvMmgDZ8ow4SOlyFjVFNSkAWkY45CgscWDj qIq6UqantsJPG7mLQ2PLslKARw== X-Google-Smtp-Source: ABdhPJw/gCmD6ATojv0o8JhVPZIKX3IrwWRm5+0wGnmnsfoJaDMuZnuVhVdQjluwsYZsDYjC7LRvWw== X-Received: by 2002:a1c:bbc5:: with SMTP id l188mr12304036wmf.163.1590144878440; Fri, 22 May 2020 03:54:38 -0700 (PDT) Return-Path: Received: from vanye ([2001:470:1f09:12f0:b26e:bfff:fea9:f1b8]) by smtp.gmail.com with ESMTPSA id s19sm5490759wmj.21.2020.05.22.03.54.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 May 2020 03:54:37 -0700 (PDT) Date: Fri, 22 May 2020 11:54:35 +0100 From: "Leif Lindholm" To: Laszlo Ersek Cc: devel@edk2.groups.io, ard.biesheuvel@arm.com, glin@suse.com, liming.gao@intel.com Subject: Re: [edk2-devel] [PATCH v2] ArmPkg/CompilerIntrinsicsLib: provide atomics intrinsics Message-ID: <20200522105435.GY1923@vanye> References: <20200520114448.26104-1-ard.biesheuvel@arm.com> <20200521112353.GS1923@vanye> <20200521131644.GT1923@vanye> <059e1db5-8228-63a8-09ab-bb0efcd95176@arm.com> <20200521141615.GU1923@vanye> <036f7682-0903-40aa-3743-6a383b742b88@redhat.com> MIME-Version: 1.0 In-Reply-To: <036f7682-0903-40aa-3743-6a383b742b88@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 21, 2020 at 22:22:58 +0200, Laszlo Ersek wrote: > 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" That isn't actually exatly what I meant - I meant properly obsolete as in "we are now reasonably certain no one is still using some silly ancient cross compiler they checked into their build infrastructure years ago". > , 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). But I don't object to that approach. Regards, Leif