Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: disable libitm for sparc <v9
Date: Thu, 15 Jan 2015 07:37:02 -0300	[thread overview]
Message-ID: <54B7984E.7090705@zacarias.com.ar> (raw)
In-Reply-To: <20150115093742.1fb23f1f@free-electrons.com>

On 01/15/2015 05:37 AM, Thomas Petazzoni wrote:

> Applied, thanks. Is it only SPARCv8 that doesn't have libitm support,
> or could other architectures be affected? If other architectures are
> affected, we may want to introduce a BR2_ARCH_HAS_LIBITM or some other
> similar thing.
> 
> Another weird thing: we're not enabling libitm, so why is gcc enabling
> it by itself, if it knows that the architecture cannot support it?

There are other architectures that could be affected, most notably old
processors/cores.
I don't think we need to do anything more special about it, most of the
time gcc will detect and enable it if the architecture supports it,
which basically boils down to your second question, it's failing to
realize sparc v8 can't handle it.
It probably has to do with the sparc tuple being used for sparc64 as
well (64 bit kernel 32 bit userland) and sparc v8 being terribly old and
hardly used outside of LEON (V9 dates from 1993!).
Regards.

      reply	other threads:[~2015-01-15 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  0:29 [Buildroot] [PATCH] package/gcc: disable libitm for sparc <v9 Gustavo Zacarias
2015-01-15  8:37 ` Thomas Petazzoni
2015-01-15 10:37   ` Gustavo Zacarias [this message]

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=54B7984E.7090705@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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