From: Fabio Giovagnini <fabio.giovagnini@aurion-tech.com>
To: linux-sh@vger.kernel.org
Subject: Complining with codesurgery 4.4.-43 sh2a
Date: Fri, 19 Mar 2010 11:01:23 +0000 [thread overview]
Message-ID: <201003191201.24090.fabio.giovagnini@aurion-tech.com> (raw)
Hi all, why I need to compile my code with -m2a -m2a-nofpu aven if sh2a 76203
has an fpu?
If I do not use -m2a-nofpu I have error
undefined reference to `__fpscr_values'
at linking time
Thanks
In data venerdì 19 marzo 2010 09:24:04, Magnus Damm ha scritto:
: > Hi Fabio,
>
> On Fri, Mar 19, 2010 at 2:27 PM, Fabio Giovagnini
>
> <fabio.giovagnini@aurion-tech.com> wrote:
> > Hi, could you tell me please how to find info about using qemu for sh2a
> > if it is possible?
>
> QEMU did not support sh2a last time I checked. And I doubt that anyone
> added it recently.
>
> It may however be a good idea to use QEMU to learn about initramfs and
> user space programs on a different processor or architecture.
>
> If I were you then I'd try to get QEMU working with x86 as target.
> When you have initramfs working on x86 in QEMU then you can easily
> move over to some other target. With sh2a on real hardware with an old
> kernel version there are too many unknowns to make efficient progress.
>
> Cheers,
>
> / magnus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Fabio Giovagnini
Aurion s.r.l.
P.I e C.F.
00885711200
Tel. +39.051.594.78.24
Cell. +39.335.83.50.919
next reply other threads:[~2010-03-19 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:01 Fabio Giovagnini [this message]
2010-03-19 11:27 ` Complining with codesurgery 4.4.-43 sh2a Paul Mundt
2010-03-19 11:47 ` Fabio Giovagnini
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=201003191201.24090.fabio.giovagnini@aurion-tech.com \
--to=fabio.giovagnini@aurion-tech.com \
--cc=linux-sh@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox