This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [patch] lrint/lrintf oddity
Brian Dessent wrote:
> Linux uses glibc, Cygwin uses newlib. They're not the same thing.
OK.
> Glibc is highly optimized and tweaked, newlib is designed as a small and
> portable libc for embedded systems.
Is the target small source code size or small executable size?
If its small executable size, a single inline asm instruction will be
smaller than than a function call.
> <http://cygwin.com/acronyms/#PTC>. The newlib mailing list is right
> over there -->
Thats nice, but I've already spend an unreasonably large amount of time
trying to get my project running on windows, a platform I personally
never use (other than to make source my software runs on it).
> Be aware that newlib supports a wide variety of platforms, some with no
> FPU, so you can't just go yanking stuff out.
The existing code can be kept for targets with no FPU.
> If you don't care about portability you could probably #define the
> inline asm versions of the functions.
Thats the course of action I'll take. Cygwin is currently the only
platform that I'm interested in that doesn't have a fast, working
lrint/lrintf implementation.
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
"I don't think any MS Exec will ever die of old age. Satan
doesn't need the competition."
-- Digital Wokan on LinuxToday.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/