All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: mono build error with swp instruction
Date: Wed, 07 Jan 2009 15:44:45 +0100	[thread overview]
Message-ID: <gk2f4t$as6$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0901070635q6c29b1d3xb3a00be2147e2c07@mail.gmail.com>

On 07-01-09 15:35, Cliff Brake wrote:
> I ran into an interesting build error this morning that might be worth
> documenting ...

Already known:

http://cgit.openembedded.net/cgit.cgi?url=openembedded/commit/&id=e9404d66bec8f92a9e05cda5251078460bdc9ed2

>
> When building mono with the latest toolchains built with OE, I get:
>
> /tmp/ccYsXwlg.s:3067: Error: selected processor does not support `swp
> r2,r0,[r4]'
> /tmp/ccYsXwlg.s:3161: Error: selected processor does not support `swp
> r2,r0,[r4]'
> /tmp/ccYsXwlg.s:3272: Error: selected processor does not support `swp
> r3,r4,[r5]'
>
> In the libgc code, there is the following:
>
> #    ifdef ARM32
>          inline static int GC_test_and_set(volatile unsigned int *addr) {
>            int oldval;
>            /* SWP on ARM is very similar to XCHG on x86.  Doesn't lock the
>             * bus because there are no SMP ARM machines.  If/when there are,
>             * this code will likely need to be updated. */
>            /* See linuxthreads/sysdeps/arm/pt-machine.h in glibc-2.1 */
>            __asm__ __volatile__("swp %0, %1, [%2]"
>        		  	     : "=&r"(oldval)
>        			     : "r"(1), "r"(addr)
> 			     : "memory");
>            return oldval;
>          }
>
> The solution was to set ARM_INSTRUCTION_SET = "arm" in the mono recipe.
>
> Thanks,
> Cliff
>





  reply	other threads:[~2009-01-07 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 14:35 mono build error with swp instruction Cliff Brake
2009-01-07 14:44 ` Koen Kooi [this message]
2009-01-07 16:21 ` Philip Balister

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='gk2f4t$as6$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.