Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] glib-2.0: drop add-march-i486-into-CFLAGS-automatically.patch
Date: Mon, 01 Feb 2016 22:44:41 +0000	[thread overview]
Message-ID: <1454366681.7421.37.camel@pbcl.net> (raw)
In-Reply-To: <56AFDAC5.9000008@windriver.com>

On Mon, 2016-02-01 at 17:23 -0500, Randy MacLeod wrote:
> Do you remember why this patch was needed?

The comments in the patch provide a fairly clear explanation of what
problem it was trying to solve.  But I agree with Andre that this cure
is in fact worse than the original disease.

In any case, the issue is probably moot because neither glibc nor musl
support cpus without cmpxchg any more.

p.




  reply	other threads:[~2016-02-01 22:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 23:28 [PATCH 0/3] glib-2.0: minor fixes and updates Andre McCurdy
2016-01-27 23:28 ` [PATCH 1/3] glib-2.0: refresh configure-libtool.patch Andre McCurdy
2016-01-27 23:28 ` [PATCH 2/3] glib-2.0: drop add-march-i486-into-CFLAGS-automatically.patch Andre McCurdy
2016-02-01 22:23   ` Randy MacLeod
2016-02-01 22:44     ` Phil Blundell [this message]
2016-02-03  8:07       ` Huang, Jie (Jackie)
2016-01-27 23:28 ` [PATCH 3/3] glib.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5 Andre McCurdy
2016-03-03 13:02   ` Phil Blundell
2016-03-03 13:18     ` Martin Jansa
2016-03-03 14:00       ` Phil Blundell
2016-03-03 19:11         ` Andre McCurdy
2016-03-03 19:30           ` Phil Blundell

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=1454366681.7421.37.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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