Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vpowf parameters backwards on Intel?




On Apr 27, 2006, at 3:12 PM, David Gohara wrote:


On Apr 24, 2006, at 5:57 PM, Ian Ollmann wrote:

go. I'm imagining something like the code below. You could also do version testing on vecLib, except that it isn't known precisely what the version number will be that fixes the problem.

What is the proper method of determining which version of vecLib is available on a system? I have some code that I want to use vForce for, but I need the code to run on 10.3 as well. Rather than compile two versions of the program, is there a way to determine if vForce is available and if so use it, otherwise use the fallback function?

Use -weak_framework Accelerate, and then test to see if the function you want to use is non-NULL before calling it.


http://developer.apple.com/documentation/MacOSX/Conceptual/ BPFrameworks/Concepts/WeakLinking.html

Ian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
PerfOptimization-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/perfoptimization-dev/email@hidden

This email sent to email@hidden
References: 
 >vpowf parameters backwards on Intel? (From: glenn andreas <email@hidden>)
 >Re: vpowf parameters backwards on Intel? (From: Ian Ollmann <email@hidden>)
 >Re: vpowf parameters backwards on Intel? (From: John Stiles <email@hidden>)
 >Re: vpowf parameters backwards on Intel? (From: Ian Ollmann <email@hidden>)
 >Re: vpowf parameters backwards on Intel? (From: David Gohara <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.