• 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: Coreaudio-api Digest, Vol 1, Issue 66
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coreaudio-api Digest, Vol 1, Issue 66


  • Subject: Re: Coreaudio-api Digest, Vol 1, Issue 66
  • From: alex <email@hidden>
  • Date: Tue, 9 Nov 2004 10:06:11 -0500

You could always be explicit and 'inline asm' the VRSAVE code yourself if you know how many registers you are using but it sounds like you may not based on the fact that you are using the compiler intrinsics and therefore the compiler is doing the register allocations.

alex

At 8:37 AM +0000 11/9/04, Os wrote:
>Hi,
>
>I'm using latest XCode, gcc 3.3, no inline assembly (just compiler intrinsics).
>
>I have some sizeable inlined functions, and very heavy altivec register usage (roll on VMX128) but nothing particularly evil.
>
>
>cheers,
>os.
>
>On 8 Nov 2004, at 20:03, email@hidden wrote:
>
>>As for the original question, if os is only using inline assembly,
>>*maybe* gcc lets you sneak through altivec code even if "-faltivec" is
>>not specified.  The gcc in-line assembly is too grotesque for me to
>>just try this theory.  :-)  os, what version of the tools are you using
>>to build your code?
>>
>email@hidden
>http://www.collective.co.uk/
>
>_______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Coreaudio-api mailing list      (email@hidden)
>Help/Unsubscribe/Update your Subscription:
>
>This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Coreaudio-api Digest, Vol 1, Issue 66
      • From: Os <email@hidden>
References: 
 >Re: Coreaudio-api Digest, Vol 1, Issue 66 (From: Os <email@hidden>)

  • Prev by Date: Questions about HAL API.
  • Next by Date: Re: Questions about HAL API.
  • Previous by thread: Re: Coreaudio-api Digest, Vol 1, Issue 66
  • Next by thread: Re: Coreaudio-api Digest, Vol 1, Issue 66
  • Index(es):
    • Date
    • Thread