All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Smart - "Illegal instruction"
Date: Fri, 24 Jan 2014 10:28:06 -0600	[thread overview]
Message-ID: <52E29496.3050501@windriver.com> (raw)
In-Reply-To: <CAJTo0LZs6rkCsAxKuHkKoRFOY12TYs3WcVU5dmxSv5V+YFZJxA@mail.gmail.com>

On 1/24/14, 4:26 AM, Burton, Ross wrote:
> On 24 January 2014 10:21,  <yoctolist@progserv.de> wrote:
>> Do I have to define a new BSP?
>>
>> Did anyone have a similar problem and could give me some advice?
>
> IIRC, genericx86 targets Atom and higher (the README lists the target
> hardware) so it's quite possible that the compiler is emitting
> instructions that your CPU doesn't actually have.  You could create a
> new BSP, or edit the tune flags from your distro or local
> configuration to target your CPU.

I believe that this AMD Sempron processor is using an older instruction set.  So 
as Ross indicated, the best approach is to define a correct tune and BSP for 
your part.

Looking at what I found online, it appears the Sempron 2100 supports:

MMX, 3DNow!, SSE, SSE2, SSE3, AMD64 and EVP

The atom tune is compatible with the core2 tune.  The core2 supports

MMX, SSE, SSE2, SSE3, SSE4.1, and Supplemental SSE3

So my guess is that last two items is the issue.  If you copy the genericx86 BSP 
and modify the configuration to use the tune-x86_64.inc instead, that may fix 
your issue.

--Mark

> Ross
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



  reply	other threads:[~2014-01-24 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 10:21 Smart - "Illegal instruction" yoctolist
2014-01-24 10:26 ` Burton, Ross
2014-01-24 16:28   ` Mark Hatle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-25 15:17 yoctolist

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=52E29496.3050501@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=yocto@yoctoproject.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.