• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
%vx? Re: AltiVec on OSX in Cocoa
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

%vx? Re: AltiVec on OSX in Cocoa


  • Subject: %vx? Re: AltiVec on OSX in Cocoa
  • From: Jake <email@hidden>
  • Date: Sun, 11 Nov 2001 08:28:17 -0500 (EST)

Thank you all for the contribution about the altivec usage, watchouts, and
code snippets. A few things that I am still a little baffled:

One of the tutorials online recommends that one also add the flag

-force-cpusubtype_ALL

is that option necessary as well(just -faltivec worked fine for me)
Yes, I tried the apple documentations; however, in spite of popular
belief, the word "altivec" is not mentioned at all in
/Developer/Documentation/DeveloperTools/Compiler/Compiler.pdf

secondly, the http://developer.apple.com/hardware/ve/tutorial.html
suggests the availability of %v[x] format strings for printf. Those
doesn't seem to work either under project builder. So does that mean
those flag has not made their way to libc in OSX no?

At last, what is the suggest approach in profiling one's objC code? I have
tried Sampler and a few other tools that is in the /Developer/Application
directory. It seems most of the time my code is stuck on [objc msgsend]
etc.(the same issue with the debugger). Is that the price one pays
for a dynamic systems over static call graphs? Does it make sense for one
to write all the vector code in straight C and then use cocoa to wrap
them?


Thanks again.
Jake


References: 
 >Re: AltiVec on OSX in Cocoa (From: Brendan Younger <email@hidden>)

  • Prev by Date: Re: Putting files in Trash
  • Next by Date: Re: AltiVec on OSX in Cocoa
  • Previous by thread: gcc 3.0.x
  • Next by thread: Re: AltiVec on OSX in Cocoa
  • Index(es):
    • Date
    • Thread