Displaying 3 results from an estimated 3 matches for "poutput".
Did you mean:
output
2012 Nov 07
0
[LLVMdev] Problem migrating from llvm 2.9 to 3.0
...fir2dim.ll
> llvm-as fir2dim.ll
> opt -O3 fir2dim.bc > fir2dim.opt.bc
> llvm-dis fir2dim.opt.bc
>
> Any idea why this is happening ?
maybe it completely unrolled this loop:
for (i = 0 ; i < 9 ; i++) {
*poutput += *pcoeff++ * *(parray++ +(i
/ 3) * ARRAYDIM) ;
}
?
Ciao, Duncan.
2012 Nov 07
2
[LLVMdev] Problem migrating from llvm 2.9 to 3.0
Hello, I'm moving a compiler pass from llvm 2.9 to 3.0, and I'm getting
some strange extra store instructions when optimizing the code.
For example, in the code that is in the attachments (On block *for.body111* for
2.9 and block *for.body67 *for 3.0), the number of stores goes from 1 to
10. And since the compiler pass adds some verification code before each
store, this leads to some
2007 Aug 23
0
[ANNOUNCE] xf86-video-ati 6.7.191
...bring over setproperty from intel code
fixup mode probing a bit neater
rename some variables to output from connector
get rid of mergetype and displaytype from radeon.h
remove all the locking glxgears runs fine over screen changes without it
remove assignments to pOutput before it is created
David Woodhouse (1):
Fix radeon vs fbdev pitch calculation.
Eamon Walsh (2):
Convert callers of LookupWindow() to dixLookupWindow().
Revert "Convert callers of LookupWindow() to dixLookupWindow()."
George Sapountzis (48):
Bug 6242: [mach64]...