From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Complining with codesurgery 4.4.-43 sh2a
Date: Fri, 19 Mar 2010 11:27:35 +0000 [thread overview]
Message-ID: <20100319112734.GG10003@linux-sh.org> (raw)
In-Reply-To: <201003191201.24090.fabio.giovagnini@aurion-tech.com>
On Fri, Mar 19, 2010 at 12:01:23PM +0100, Fabio Giovagnini wrote:
> 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
>
You should never be touching any of the Makefile build flags, they are
delicate, have rigid ordering requirements, and are mapped out the way
they are intentionally. Any time you are forced to hack up build flags
you are almost guaranteed to be doing something wrong.
Whether the CPU has an FPU or not is completely irrelevant from the
context of the kernel. The kernel does not have its own FP state, and so
can't handle having FP instructions generated by the compiler, this is
what the -nofpu inhibiting is for. Even in situations where the kernel
may wish to hand craft FP context and open code a few instructions, the
kernel is never built without -nofpu.
next prev parent reply other threads:[~2010-03-19 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 11:01 Complining with codesurgery 4.4.-43 sh2a Fabio Giovagnini
2010-03-19 11:27 ` Paul Mundt [this message]
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=20100319112734.GG10003@linux-sh.org \
--to=lethal@linux-sh.org \
--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