From: "Leif Lindholm" <leif@nuviainc.com>
To: Laszlo Ersek <lersek@redhat.com>
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
Date: Fri, 22 May 2020 11:54:35 +0100 [thread overview]
Message-ID: <20200522105435.GY1923@vanye> (raw)
In-Reply-To: <036f7682-0903-40aa-3743-6a383b742b88@redhat.com>
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
next prev parent reply other threads:[~2020-05-22 10:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 11:44 [PATCH v2] ArmPkg/CompilerIntrinsicsLib: provide atomics intrinsics Ard Biesheuvel
2020-05-20 12:37 ` [edk2-devel] " Philippe Mathieu-Daudé
2020-05-21 16:40 ` Philippe Mathieu-Daudé
2020-05-21 16:45 ` Ard Biesheuvel
2020-05-21 16:59 ` Philippe Mathieu-Daudé
2020-05-21 17:02 ` Ard Biesheuvel
2020-05-21 17:07 ` Philippe Mathieu-Daudé
2020-05-20 15:59 ` Laszlo Ersek
2020-05-21 11:23 ` Leif Lindholm
2020-05-21 12:58 ` [edk2-devel] " Ard Biesheuvel
2020-05-21 13:16 ` Leif Lindholm
2020-05-21 13:31 ` Ard Biesheuvel
2020-05-21 14:16 ` Leif Lindholm
2020-05-21 20:22 ` Laszlo Ersek
2020-05-22 8:16 ` Ard Biesheuvel
2020-05-22 10:54 ` Leif Lindholm [this message]
2020-05-22 13:27 ` Ard Biesheuvel
2020-05-22 19:04 ` Laszlo Ersek
2020-06-02 0:50 ` Liming Gao
2020-06-02 7:09 ` Ard Biesheuvel
2020-05-28 1:36 ` Gary Lin
2020-05-28 9:49 ` Leif Lindholm
2020-05-28 15:48 ` Liming Gao
2020-05-28 20:09 ` Laszlo Ersek
2020-05-29 3:04 ` Liming Gao
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-list 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=20200522105435.GY1923@vanye \
--to=devel@edk2.groups.io \
/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