From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: Hi all, how could I check if my compiler use fpu instruction?
Date: Tue, 29 Jan 2008 00:49:56 +0000 [thread overview]
Message-ID: <20080129004956.GC9937@linux-sh.org> (raw)
In-Reply-To: <200801282208.08210.fabio.giovagnini@aurion-tech.com>
It is incredibly difficult to reply to your mail when you insist on
putting the body of your text in the subject line. Please use a more
meaningful subject and actually use the body for something other than
your .sig, thanks.
Regarding FP use, this depends on your target, and on your CFLAGS. If
you're using a target that supports an FPU, FP instructions are generated
by default. You will need to explicitly inhibit FP instruction generation
if you do not want it. You can look at arch/sh/Makefile for various ways
we try to prevent the compiler from generating FP instructions ("try" is
operative here, since GCC often has its own ideas about things).
next prev parent reply other threads:[~2008-01-29 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 21:08 Hi all, how could I check if my compiler use fpu instruction? Fabio Giovagnini
2008-01-29 0:49 ` Paul Mundt [this message]
2008-01-29 8:32 ` 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=20080129004956.GC9937@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