All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too
Date: Thu, 3 Mar 2016 00:04:52 -0600	[thread overview]
Message-ID: <56D7D404.4090500@windriver.com> (raw)
In-Reply-To: <1456981633-16756-1-git-send-email-armccurdy@gmail.com>

On 3/2/16 11:07 PM, Andre McCurdy wrote:
> libitm is already disabled for big endian MIPS, but needs to be
> disabled for little endian MIPS targets too.

No objection to the patch, but do we have any little endian MIPS currently
defined or buildable to test?

All of the samples I've seen are all big endian these days.  (QEMU or actual
boards.)

--Mark

> Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
> ---
>  meta/recipes-devtools/gcc/gcc-runtime.inc | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta/recipes-devtools/gcc/gcc-runtime.inc b/meta/recipes-devtools/gcc/gcc-runtime.inc
> index 707db37..1c3dd54 100644
> --- a/meta/recipes-devtools/gcc/gcc-runtime.inc
> +++ b/meta/recipes-devtools/gcc/gcc-runtime.inc
> @@ -12,7 +12,9 @@ EXTRA_OECONF_append_linuxstdbase = " --enable-clocale=gnu"
>  
>  RUNTIMELIBITM = "libitm"
>  RUNTIMELIBITM_mips = ""
> +RUNTIMELIBITM_mipsel = ""
>  RUNTIMELIBITM_mips64 = ""
> +RUNTIMELIBITM_mips64el = ""
>  
>  RUNTIMETARGET = "libssp libstdc++-v3 libgomp libatomic ${RUNTIMELIBITM} \
>      ${@bb.utils.contains_any('FORTRAN', [',fortran',',f77'], 'libquadmath', '', d)} \
> 



  reply	other threads:[~2016-03-03  6:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  5:07 [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too Andre McCurdy
2016-03-03  6:04 ` Mark Hatle [this message]
2016-03-03  6:24   ` Khem Raj
2016-03-03  6:42     ` Andre McCurdy

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=56D7D404.4090500@windriver.com \
    --to=mark.hatle@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.