search for: resx

...a vector as follows: > head(res) 1007_s_at.value 1053_at.value 117_at.value 121_at.value 1255_g_at.value 0.225801033 0.009747404 0.709517954 0.008825740 0.496859178 1294_at.value 0.005091231 after I convert the res into a data frame I got the following: resx<- data.frame(res) > head(resx) res 1007_s_at.value 0.225801033 1053_at.value 0.009747404 117_at.value 0.709517954 121_at.value 0.008825740 1255_g_at.value 0.496859178 1294_at.value 0.005091231 as you may see, the first column of resx has no names and it d...

...d casted back to float. Unfortunately, in my case, LLVM seems to be unable to remove this kind of code (in more complex functions of course) even though it gets inlined and optimized. I end up with functions like this one: define void @xyz(float %aX, float %aY, float %aZ, float* noalias nocapture %resX, float* noalias nocapture %resY, float* noalias nocapture %resZ) nounwind { entry: %0 = fadd float %aZ, 5.000000e-01 ; <float> [#uses=1] %1 = fadd float %aY, 5.000000e-01 ; <float> [#uses=1] %2 = fadd float %aX, 5.000000e-01 ; <float> [#uses=1] %...

...%0, align 4 > ret void > } it is reasonable to expect the optimizers to turn this at least into %tmp8 = bitcast double %a.0 to i64 %tmp2 = lshr i64 %tmp8, 32 %tmp3 = bitcast i32 %tmp2 to float > define void @xyz(float %aX, float %aY, float %aZ, float* noalias > nocapture %resX, float* noalias nocapture %resY, float* noalias > nocapture %resZ) nounwind { > entry: > %0 = fadd float %aZ, 5.000000e-01 ; <float> [#uses=1] > %1 = fadd float %aY, 5.000000e-01 ; <float> [#uses=1] > %2 = fadd float %aX, 5.000000e-01 ; &l...

Hi Ralf, > I do not understand why this behaviour is required. What is the problem > in having a function receive a single struct-parameter with three floats > compared to two scalar parameters? > > source-code (C++): > struct Test3Float { float a, b, c; }; > void test(Test3Float param, Test3Float* result) { ... } if you compile this with GCC, you will see that it too

Uh, sorry, did not pay attention where I was replying ;) Hey Duncan, I do not understand why this behaviour is required. What is the problem in having a function receive a single struct-parameter with three floats compared to two scalar parameters? source-code (C++): struct Test3Float { float a, b, c; }; void test(Test3Float param, Test3Float* result) { ... } bitcode:

...s 1" error. (The printer remains "ready" now, even after the job fails.) So I set LogLevel debug as suggested and this appears to be the relevent part of the output: D [04/Feb/2007:21:45:18 -0800] [Job 6] renderer command: lz11.foomatic --papersize=letter --color=0 --inksaving=1 --resx=582 --resy=582 D [04/Feb/2007:21:45:18 -0800] [Job 6] renderer return value: 16777215 D [04/Feb/2007:21:45:18 -0800] [Job 6] renderer received signal: 16777215 D [04/Feb/2007:21:45:18 -0800] [Job 6] Process dying with "The renderer command line returned an unrecognized error code 16777215.&quo...

The attached patch cleans up Opus's x86 intrinsics configury. It: * Makes ?enable-intrinsics work with clang and other non-GCC compilers * Enables RTCD for the floating-point-mode SSE code in Celt. * Disables use of RTCD in cases where the compiler targets an instruction set by default. * Enables the SSE4.1 Silk optimizations that apply to the common parts of Silk when Opus is built in