From: "Leif Lindholm" <leif@nuviainc.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
devel@edk2.groups.io, liming.gao@intel.com, philmd@redhat.com,
mliska@suse.cz
Subject: Re: [edk2-devel] [PATCH] MdePkg/Include: AARCH64: disable outline atomics on GCC 10.2+
Date: Thu, 28 May 2020 11:05:15 +0100 [thread overview]
Message-ID: <20200528100515.GC1923@vanye> (raw)
In-Reply-To: <0f2f90b9-e2fe-5658-e507-299a387e0ce5@redhat.com>
On Wed, May 27, 2020 at 11:12:23 +0200, Laszlo Ersek wrote:
> >>> Oh and I think both this patch and the assembly language implementation
> >>> for the atomics should be delayed after the stable tag. gcc-10 is a new
> >>> toolchain; so even if we don't introduce a new toolchain tag such as
> >>> GCC10 for it, whatever we do in order to make it work, that's feature
> >>> enablement in my book.
> >>
> >> Works for me. By the time the next stable tag comes around, early adopters
> >> that are now on GCC 10.1 will likely have moved to 10.2 by that time, and so
> >> we may not need the assembly patch at all.
> >
> > I'm not ecstatic that we'll be releasing the first stable tag known to
> > break with current toolchains.
>
> If this breakage affects "current toolchains", then why was
> <https://bugzilla.tianocore.org/show_bug.cgi?id=2723> only reported on
> 2020-May-19, four days into the soft feature freeze?
I agree the timing is crap.
> > This isn't just affecting random crazies pulling latest toolchains
> > down, but people using their distro defaults (native or cross).
>
> ... "people using their distro defaults" to *not* build upstream edk2
> until 2020-May-19, apparently.
Or distro defaults changing in between. I mean, we could say "Arch
is the same as any other distro's unstable", but I wouldn't want to go
down that route - I know people who use it for developing also for
qemu and linux.
Argh, I also just realised the error report I saw two days after
Ard's intrinsics patch hit the list was not a public report. Yes, if
this had affected only in-development/unstable distributions, I agree
this isn't something we should try to deal with upstream.
> > I don't recall if 10.1 ended up being default in F32, but it was
> > definitely included. In Arch, it does appear default.
> >
> > Debian/Ubuntu are unaffected in their stable releases.
> >
> > I agree it's a transitional issue, but I would really prefer to have
> > the intrinsics included in the release.
>
> OK, let's delay the release then, by a few days. I agree the present
> patch may qualify as a bugfix, but the other patch with the assembly
> language intrinsics doesn't. If it's really that important to have in
> the upcoming stable tag, then it's worth delaying the tag for. I'm fine
> delaying the release for it; it wouldn't be without precedent.
I would argue it *is* a bugfix, since it only has an effect on builds
that would otherwise fail. But I also do think it is important enough
to delay the release if we feel that is necessary.
/
Leif
> Also, I think Ard's assembly language patch needs a Tested-by from Gary
> at the least (reporter of TianoCore#2723). Please reach out to him in
> that thread.
>
> ... More precisely, please *ping* Gary for a Tested-by in that thread,
> because Ard CC'd him from the start, and even credited Gary in the
> commit message.
>
> Thanks,
> Laszlo
>
next prev parent reply other threads:[~2020-05-28 10:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 10:12 [PATCH] MdePkg/Include: AARCH64: disable outline atomics on GCC 10.2+ Ard Biesheuvel
2020-05-22 11:41 ` Leif Lindholm
2020-05-22 12:05 ` Ard Biesheuvel
2020-05-22 12:14 ` Leif Lindholm
2020-05-22 12:42 ` Ard Biesheuvel
2020-05-22 13:01 ` Leif Lindholm
2020-05-22 20:01 ` Laszlo Ersek
2020-05-22 20:05 ` Laszlo Ersek
2020-05-22 22:09 ` [edk2-devel] " Ard Biesheuvel
2020-05-26 14:37 ` Leif Lindholm
2020-05-27 9:12 ` Laszlo Ersek
2020-05-27 9:30 ` Gary Lin
2020-05-28 10:05 ` Leif Lindholm [this message]
2020-05-28 20:03 ` Laszlo Ersek
2020-05-29 3:18 ` Liming Gao
2020-05-29 5:46 ` Ard Biesheuvel
2020-05-29 14:29 ` Liming Gao
2020-05-29 16:51 ` Ard Biesheuvel
2020-05-30 15:10 ` Liming Gao
2020-05-30 15:22 ` Leif Lindholm
2020-05-30 15:32 ` Liming Gao
2020-05-30 16:18 ` Leif Lindholm
2020-06-01 10:31 ` Ard Biesheuvel
2020-06-01 14:35 ` 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=20200528100515.GC1923@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