From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [patch][5/5] powerpc V2: Add the general support for Embedded Floating-Point instructions
Date: Fri, 9 Feb 2007 15:40:07 +0100 [thread overview]
Message-ID: <543c39e820836fcfe2d93681a0657d57@kernel.crashing.org> (raw)
In-Reply-To: <3E83A767-0E8C-41E3-A9C7-A231CD841EAF@kernel.crashing.org>
>>> I thought we were going to have some general Kconfig option
>>> to enable all this? EMDEDDED_FP_IEEE or something like that
>>
>> So that users have chance to enable/disable fully IEEE compliance?
>> Segher
>> had mentioned this, and it sounds reasonable.
>
> Its alot of code to bring in if you don't care about IEEE compliance.
Yes certainly, and that's important for embedded applications.
My point however is that this should be selectable *per process*
at runtime. Compare to the AltiVec situation (where processes
can select (non-)IEEE behaviour by themselves); most tasks do
*not* want IEEE behaviour as it is just too expensive (and not
necessary for many applications).
Segher
next prev parent reply other threads:[~2007-02-09 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 3:55 [patch][5/5] powerpc V2: Add the general support for Embedded Floating-Point instructions ebony.zhu
2007-02-08 7:32 ` Kumar Gala
2007-02-08 9:06 ` Zhu Ebony-r57400
2007-02-08 17:31 ` Kumar Gala
2007-02-09 5:15 ` Zhu Ebony-r57400
2007-02-09 5:28 ` Kumar Gala
2007-02-09 5:48 ` Zhu Ebony-r57400
2007-02-09 6:03 ` Kumar Gala
2007-02-09 6:27 ` Zhu Ebony-r57400
2007-02-09 14:40 ` Segher Boessenkool [this message]
2007-03-08 7:04 ` Zhu Ebony-r57400
2007-02-22 12:48 ` Sergei Shtylyov
2007-02-22 13:43 ` Sergei Shtylyov
2007-02-22 16:36 ` Segher Boessenkool
2007-02-22 16:56 ` Sergei Shtylyov
2007-02-22 18:22 ` Kumar Gala
2007-03-08 7:12 ` [patch][5/5] powerpc V2: Add the general support for EmbeddedFloating-Point instructions Zhu Ebony-r57400
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=543c39e820836fcfe2d93681a0657d57@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).