Re: Finding the user's processor type...
Re: Finding the user's processor type...
- Subject: Re: Finding the user's processor type...
- From: Markus Hitter <email@hidden>
- Date: Mon, 28 Nov 2005 11:17:06 +0100
Am 28.11.2005 um 03:44 schrieb Mr Chris Giddings:
With the advent of the Intel based machinery it seems there isn't a
methodology for interpreting the user's processor type with gestalt.
You mean there's hope people stop trying to write processor-specific
code or even trying to prevent users on specific machines to use some
apps at all? If that's the case, I'm all with Apple.
There's very very rarely a need to find out something about the
processor. Performance increases due to different compiler flags on
different machines are neglible for average computing. Preventing
specific processors from executing an app is just nonsense.
If you are after the last few perfomance-percents, use Mac OS X
system libs as they already speed up computation if specific
hardware, e.g. AltiVec is present.
If you are after stuff like endianness of ints and floats, use the
macros provides in the system lib headers, e.g.
CFSwapInt16LittleToHost(). There's __BIG_ENDIAN__ and
__LITTLE_ENDIAN__ as well.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden