public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>
Cc: devel@edk2.groups.io, lersek@redhat.com, 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: Tue, 26 May 2020 15:37:25 +0100	[thread overview]
Message-ID: <20200526143725.GM1923@vanye> (raw)
In-Reply-To: <5587f0f0-9f30-62ce-9d07-5eed4ac6daa7@arm.com>

On Sat, May 23, 2020 at 00:09:52 +0200, Ard Biesheuvel wrote:
> > > > diff --git a/MdePkg/Include/AArch64/ProcessorBind.h b/MdePkg/Include/AArch64/ProcessorBind.h
> > > > index 896bf273ac7a..a3ca8f09e51c 100644
> > > > --- a/MdePkg/Include/AArch64/ProcessorBind.h
> > > > +++ b/MdePkg/Include/AArch64/ProcessorBind.h
> > > > @@ -24,6 +24,17 @@
> > > >   #pragma pack()
> > > >   #endif
> > > > +#if defined(__GNUC__) && !defined(__clang__)
> > > > +
> > > > +//
> > > > +// Disable GCC outline atomics
> > > > +// Link: https://bugzilla.tianocore.org/show_bug.cgi?id=2723
> > > > +//
> > > > +#if __GNUC__ > 10 || (__GNUC__ == 10 && __GNUC_MINOR__ >= 2)
> > > > +#pragma GCC target "no-outline-atomics"
> > > > +#endif
> > > > +#endif
> > > > +
> > > >   #if defined(_MSC_EXTENSIONS)
> > > >   //
> > > 
> > > Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> > > 
> > > But I think it should be merged later, after GCC 10.2 is out.
> > > 
> > > (Obviously I don't "insist" that we follow this approach, I'm just OK
> > > with it.)
> > 
> > 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.

This isn't just affecting random crazies pulling latest toolchains
down, but people using their distro defaults (native or cross).
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.

/
    Leif

  reply	other threads:[~2020-05-26 14:37 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 [this message]
2020-05-27  9:12         ` Laszlo Ersek
2020-05-27  9:30           ` Gary Lin
2020-05-28 10:05           ` Leif Lindholm
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=20200526143725.GM1923@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