From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Juro Bystricky <juro.bystricky@intel.com>
Cc: jurobystricky@hotmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] glibc: Allow 64 bit atomics for x86
Date: Thu, 29 Oct 2015 22:20:00 +0000 [thread overview]
Message-ID: <1446157200.4521.40.camel@linuxfoundation.org> (raw)
In-Reply-To: <1446151418-16034-2-git-send-email-juro.bystricky@intel.com>
On Thu, 2015-10-29 at 13:43 -0700, Juro Bystricky wrote:
> This patch fixes [YOCTO#8140].
>
> The fix consist of allowing 64bit atomic ops for x86.
> This should be safe for i586 and newer CPUs.
> It also makes the synchronization more efficient.
>
> Signed-off-by: Juro Bystricky <juro.bystricky@intel.com>
> ---
> .../glibc/glibc/use_64bit_atomics.patch | 24 ++++++++++++++++++++++
> meta/recipes-core/glibc/glibc_2.22.bb | 1 +
> 2 files changed, 25 insertions(+)
> create mode 100644 meta/recipes-core/glibc/glibc/use_64bit_atomics.patch
Since the patch is only changing nativesdk 32 bit x86 and we know that
the 32 bit SDK is pretty broken at the moment I've merged this on the
basis that it can't really make it any worse. There is pressure to move
to the next rc candidate for 2.0.
I would like to get to the bottom of the real issue here and I still
suspect 32 bit x86 images are likely broken too :/.
Cheers,
Richard
next prev parent reply other threads:[~2015-10-29 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 20:43 [PATCH 0/1] Allow 64 bit atomics in glibc 2.22 for 32bit SDK Juro Bystricky
2015-10-29 20:43 ` [PATCH 1/1] glibc: Allow 64 bit atomics for x86 Juro Bystricky
2015-10-29 21:00 ` Mark Hatle
2015-10-29 21:31 ` Bystricky, Juro
2015-10-29 22:20 ` Richard Purdie [this message]
2015-10-29 22:29 ` Randy Witt
2015-10-30 7:13 ` Richard Purdie
2015-10-30 16:02 ` Bystricky, Juro
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-all 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=1446157200.4521.40.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=juro.bystricky@intel.com \
--cc=jurobystricky@hotmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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