search for: altivec

...edu > > > > Sent: Thursday, January 31, 2013 9:26:15 AM > > > > Subject: [LLVMdev] Getting command line options to affect subtarget features > > > > > > > > The problem I'm trying to solve: Invoking clang on PowerPC with > > > > -fno-altivec has no effect. > > > > > > > > From what I've been able to piece together, PPC.td specifies various > > > > CPUs and the processor features available on each. So for example we > > > > have: > > > > > > > > def FeatureAl...

...gt; Sent: Thursday, January 31, 2013 9:26:15 AM > > > > > Subject: [LLVMdev] Getting command line options to affect subtarget features > > > > > > > > > > The problem I'm trying to solve: Invoking clang on PowerPC with > > > > > -fno-altivec has no effect. > > > > > > > > > > From what I've been able to piece together, PPC.td specifies various > > > > > CPUs and the processor features available on each. So for example we > > > > > have: > > > > > > &gt...

Hello, I'm using Mono with experimental LLVM backend support on PowerPC. I noticed that although LLVM's IR contains SIMD instructions the assembly produced doesn't contain any Altivec instructions and my PowerPC970 machine of course has Altivec support. Isn't there some kind of autodetection? I searched in Target sources but only found out that Altivec is disabled by default. Can I turn Altivec support on (and off, I need both cases) from the code? Some info: Mono's uti...

...vnet.ibm.com> > > To: llvmdev at cs.uiuc.edu > > Sent: Thursday, January 31, 2013 9:26:15 AM > > Subject: [LLVMdev] Getting command line options to affect subtarget features > > > > The problem I'm trying to solve: Invoking clang on PowerPC with > > -fno-altivec has no effect. > > > > From what I've been able to piece together, PPC.td specifies various > > CPUs and the processor features available on each. So for example we > > have: > > > > def FeatureAltivec : SubtargetFeature<"altivec","HasA...

...; To: llvmdev at cs.uiuc.edu > > > Sent: Thursday, January 31, 2013 9:26:15 AM > > > Subject: [LLVMdev] Getting command line options to affect subtarget features > > > > > > The problem I'm trying to solve: Invoking clang on PowerPC with > > > -fno-altivec has no effect. > > > > > > From what I've been able to piece together, PPC.td specifies various > > > CPUs and the processor features available on each. So for example we > > > have: > > > > > > def FeatureAltivec : SubtargetFeature<...

Hello, I'm using Mono with experimental LLVM backend support on PowerPC. I noticed that although LLVM's IR contains SIMD instructions the assembly produced doesn't contain any Altivec instructions and my PowerPC970 machine of course has Altivec support. Isn't there some kind of autodetection? I searched in Target sources but only found out that Altivec is disabled by default. Can I turn Altivec support on (and off, I need both cases) from the code? Some info: Mono's uti...

I saw some mail go by a bit ago about doubles-vs-floats, but I seem to have lost it. I'm interested in rewriting the mdct code using Altivec on MacOS X. Altivec doesn't support doubles, though -- the only floating point vector type is single precision floats. Vorbis currently has doubles everywhere -- is this really necessary? Doubles are supposedly faster than floats in the PPC FPU, but the Altivec unit is definitely going to b...

On Thu, 27 Jan 2005, John Steele Scott wrote: > That looks fine to me as well. However, the best solution is something which > Luca suggested a few months ago, which is to use the functions defined in > altivec.h. These are C functions which map directly to Altivec machine > instructions. I am willing to help out, but I don't find the current lpc_asm.s > very easy to follow, and my time is quite limited (my last patch to a free > software project took almost three months to get into decent sh...

--- Brady Patterson <brady@spaceship.com> wrote: > On Thu, 27 Jan 2005, John Steele Scott wrote: > > That looks fine to me as well. However, the best solution is > something which > > Luca suggested a few months ago, which is to use the functions > defined in > > altivec.h. These are C functions which map directly to Altivec > machine > > instructions. I am willing to help out, but I don't find the > current lpc_asm.s > > very easy to follow, and my time is quite limited (my last patch to > a free > > software project took almost thre...

Hey guys, I just released my new MacOSX-based OpenAL implementation...part of it is a Ogg Vorbis decoder based on the 1.0 reference libraries. I spent some time optimizing them and found that many of the hotspots in libvorbis are perfect candidates for vectorization, so I wrote Altivec versions of them. The end result? Decoding of a .ogg file is between 30 and 50% faster on a Mac with an Altivec unit over the stock reference libraries...which doesn't suck. Decoding is still a little faster even without Altivec due to some other optimizations that don't involve vector...

Sorry that it has been a while since the last altivec patch. I have noticed something interesting, and so it remains unfinished... On the ppc, even with the altivec optimizations, almost a quarter of the time is spent in FLAC__stream_encoder_process(). I finally discovered that it is because of all the integer to float conversions. Aside fro...

The problem I'm trying to solve: Invoking clang on PowerPC with -fno-altivec has no effect. >From what I've been able to piece together, PPC.td specifies various CPUs and the processor features available on each. So for example we have: def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", "true",...

Josh Coalson wrote: > --- Luca Barbato <lu_zero@gentoo.org> wrote: > >>Josh Coalson wrote: >> >>>since I don't know how to resolve this, in current CVS I have >>>checked in a system where there are src/libFLAC/ppc/as and >>>src/libFLAC/ppc/gas selected by configure. I have also checked >>>in as many patches as I could make sense of

...pecific. It's a BSD call (sysctl()), so a change to the platform-detection macros should enable it to work on other BSDs. However, I don't know what that would be, and I couldn't determine any safe way to do the check in Linux, nor do I have any way to test anything other than OS X. The altivec code itself should work on any platform with altivec. Regarding performance, command-line decoding will see a modest improvement, but it's really bottlenecked by the MD5 checking (and I don't have a clue as to how to optimize that). Real-time decoding should be improved substantially -- I&...

Hi, This patch adds Altivec-optimized implementations of oc_enc_frag_sad and oc_enc_frag_ssd. This patch is against the latest svn revision of theora-ptalarbvorm. Speeds up encode on a plant stop-motion clip on a 1 GHz PPC 7447 by ~3%, timewise. Time spent in oc_enc_frag_sad is reduced from 4.2% to 2.3% and oc_enc_frag_ssd...

Hi, I have been playing with Altivec, and I rewrote a couple of the routines in assembly. Looking at the archives, I noticed that there may already be some effort on this. Anyways... Right now, I have two routines working. They need to be cleaned up, made relocatable, and documented; otherwise, they seem to work fairly well. I...

...gt; > Like you, I don't see a lot of value in these. I think I'll decline > these. FLAC__lpc_restore_signal_asm_ia32_mmx compares 'order' argument with 4 and if it's greater then it jumps to FLAC__lpc_restore_signal_asm_ia32. I wonder why the same wasn't done for PPC/Altivec: why libFLAC compares 'order' and 8 in C code and not in asm.

Besides SPE (FSL e500v? cores) there are other powerpc processors that don't support altivec instructions so only enable them when it's 100% sure that the target has it. Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar> --- src/libFLAC/Makefile.am | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/libFLAC/Makefile.am b/src/libFLAC/Makefile.am i...

...t;> > I'll try to power up my Linux/PPC machine in the next couple of days >> > so I can test this. >> >> Any news? > > Sorry, haven't had a chance to set up that machine. Hopefully this > weekend. I have several patches, but they interfere with this ppc/altivec patch. (one of them changes lpc.h,another changes stream_decoder.c, etc). So I have to wait for your decision on this patch. BTW, one of them noticeably increases encoding speed of 16-bit files: <http://www.hydrogenaud.io/forums/index.php?s=&showtopic=101082&view=findpost&p=870431&g...

...t" <wschmidt at linux.vnet.ibm.com> > To: llvmdev at cs.uiuc.edu > Sent: Thursday, January 31, 2013 9:26:15 AM > Subject: [LLVMdev] Getting command line options to affect subtarget features > > The problem I'm trying to solve: Invoking clang on PowerPC with > -fno-altivec has no effect. > > From what I've been able to piece together, PPC.td specifies various > CPUs and the processor features available on each. So for example we > have: > > def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", > "true&...