• 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
Re: Altivec compile problem [OT ?]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Altivec compile problem [OT ?]


  • Subject: Re: Altivec compile problem [OT ?]
  • From: Andy <email@hidden>
  • Date: Fri, 14 Mar 2003 23:29:57 +0000

On Friday, Mar 14, 2003, at 19:12 Europe/London, Kurt Revis wrote:

On Friday, March 14, 2003, at 04:24 AM, Andy wrote:

Yet when using -faltivec the compiler is putting in a vrsave instruction at the very start of the main() function...

Assuming you don't have any vector declarations in main() (which you don't, if it compiles without -faltivec), this sounds like a compiler bug to me. Please file a bug with Apple:
http://developer.apple.com/bugreporter/index.html


Yes, I will, I'd like to identify which header(s) in the pre-comps is causing the trouble first though, I do suspect the problem is in that area.


A workaround might be to put all of your Altivec code into a separate static library target, and then link your main application against that library. That way you only need to turn on -faltivec for the library, not the whole app. (I've done this and it works fine.

I guess I might do that anyway, it's good advice.

Cheers
Andy.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Thoughts about streaming from disk and VM
  • Next by Date: mFormatID != kAudioFormatLinearPCM
  • Previous by thread: Altivec compile problem [OT ?]
  • Next by thread: mFormatID != kAudioFormatLinearPCM
  • Index(es):
    • Date
    • Thread