search for: d28

I was trying to install Ubuntu 7.10 on an HVM domain, when when the install kept hanging at a particular point. xm dmesg shows the following : (XEN) realmode.c:132:d28 Failed to emulate insn. (XEN) realmode.c:174:d28 Real-mode emulation failed @ 0000:00007f34: 0f 2c 06 08 6b 04 (XEN) domain_crash called from realmode.c:175 (XEN) Domain 28 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.4-unstable x86_32p debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) EIP: 000...

...myone(roots, suffix) d18 = myone(roots, suffix2) d19 = myone(roots, suffix3) d20 = myone(roots2, suffix) d21 = myone(roots2, suffix2) d22 = myone(roots2, suffix3) d23 = myone(state, roots) d24 = myone(city, roots) d25 = myone(cityst, roots) d26 = myone(inscompany, roots) d27 = myone(state, roots2) d28 = myone(city, roots2) d29 = myone(cityst, roots2) d30 = myone(inscompany, roots2) d31 = mytwo(state, roots, suffix) d32 = mytwo(city, roots, suffix) d33 = mytwo(cityst, roots, suffix) d34 = mytwo(inscompany, roots, suffix) d35 = mytwo(state, roots, suffix2) d36 = mytwo(city, roots, suffix2) d37 = m...

...references *READ_29 and *WRITE_30 test.c:11: note: created 2 versioning for alias checks. test.c:11: note: === vect_do_peeling_for_loop_bound ===Setting upper bound of nb iterations for epilogue loop to 14 test.c:11: note: LOOP VECTORIZED. The result is a very concise and very dense code: vld1.8 {d28[], d29[]}, [r5] vld3.8 {d16, d18, d20}, [r9]! vld3.8 {d17, d19, d21}, [r9] vmvn q3, q8 vmvn q15, q9 vmvn q8, q10 vsub.i8 q11, q3, q14 vsub.i8 q12, q15, q14 vsub.i8 q13, q8, q14 vst3.8 {d22, d24, d26}, [r8]! vst3.8 {d23, d25, d27}, [r8] cheers, --renato -------------- next part -------------- An...

...ef,dead>, %D17<imp-def,dead>, %D18<imp-def,dead>, %D19<imp-def,dead>, %D20<imp-def,dead>, %D21<imp-def,dead>, %D22<imp-def,dead>, %D23<imp-def,dead>, %D24<imp-def,dead>, %D25<imp-def,dead>, %D26<imp-def,dead>, %D27<imp-def,dead>, %D28<imp-def,dead>, %D29<imp-def,dead>, %D30<imp-def,dead>, %D31<imp-def,dead>, %CPSR<imp-def,dead> 0xeb000000 JIT: 0x4512e028: %R0<def> = LDR %SP, %reg0, 4, 14, %reg0, Mem:LD(4,4) [b + 0] 0xe59d0004 JIT: 0x4512e02c: %R0<def> = ADDri %R0<kill>, 10, 14,...

...") d23 = myone("state", "roots") d24 = myone("city", "roots") d25 = myone("cityst", "roots") d26 = myone("inscompany", "roots") d27 = myone("state", "roots2") d28 = myone("city", "roots2") d29 = myone("cityst", "roots2") d30 = myone("inscompany", "roots2") d31 = mytwo("state", "roots", "suffix") d32 = mytwo("city", "roots", &q...

...here it fails:"Error in plot.new() : figure margins too large" when plotting to a device created with postscript(). Plotting to the default X11 and using dev.print() works aside from the messed up layout.} daylab <- c("D3","D7","D10","D14","D28","D60") axis(side=3,labels=daylab,at=1:ncol(fcs),tick=FALSE) axis(side=2,labels=probe.2.symbol(pid),at=1:nrow(fcs),tick=FALSE) par(font.axis=1) par(font.lab=1) axis(side=4,labels=format(pp,scientific=TRUE,digits=2),at=1:nrow(fcs),tick=FALSE) par(las=0) Thanks, Bastian

...") d23 = myone("state", "roots") d24 = myone("city", "roots") d25 = myone("cityst", "roots") d26 = myone("inscompany", "roots") d27 = myone("state", "roots2") d28 = myone("city", "roots2") d29 = myone("cityst", "roots2") d30 = myone("inscompany", "roots2") d31 = mytwo("state", "roots", "suffix") d32 = mytwo("city", "roots", &q...

On 21 September 2012 09:28, Sebastien DELDON-GNB <sebastien.deldon at st.com> wrote: > declare <16 x float> @llvm.arm.neon.vmaxs.v16f32(<16 x float>, <16 x float>) nounwind readnone > > llc fails with following message: > > SplitVectorResult #0: 0x2258350: v16f32 = llvm.arm.neon.vmaxs 0x2258250, 0x2258050, 0x2258150 [ORD=3] [ID=0] > > LLVM ERROR: Do not

Renato, can you post the c code for the function and the assembly that gcc produces? Your initial example could be well handled by vectorization of strided loops (and the mentioning of VLD3(.8?)/VST3(.8?) lead me to assume that this is what happened). But the LLVM-IR you sent has a store of 0 in there ;) and strides by 4. Thanks, Arnold Vectorization of strided loops: I am using float as the

...0: add r12, r1, #48 add r3, r2, #32 vld1.64 {d20, d21}, [r3, :128] add r3, r2, #48 vld1.64 {d16, d17}, [r2, :128] add r2, r2, #16 vld1.64 {d18, d19}, [r1, :128] vld1.64 {d26, d27}, [r12, :128] add r12, r1, #32 vld1.64 {d24, d25}, [r3, :128] add r1, r1, #16 vadd.f32 q11, q9, q8 vld1.64 {d28, d29}, [r12, :128] vadd.f32 q9, q13, q12 vadd.f32 q8, q14, q10 vld1.64 {d20, d21}, [r2, :128] vld1.64 {d24, d25}, [r1, :128] add r1, r0, #48 vadd.f32 q10, q12, q10 vst1.64 {d22, d23}, [r0, :128] vst1.64 {d18, d19}, [r1, :128] add r1, r0, #32 add r0, r0, #16 vst1.64 {d16, d17}, [r1, :128]...

Hi, I have this bug when I activate java-6-jdk on Tomcat 5.5.26 in a Lenny Guest : Jul 31 21:24:15 tomcat01 kernel: 1 multicall(s) failed: cpu 3 Jul 31 21:24:15 tomcat01 kernel: call 1/1: op=14 arg=[b7f1a000] result=-22 Jul 31 21:24:15 tomcat01 kernel: ------------[ cut here ]------------ Jul 31 21:24:15 tomcat01 kernel: kernel BUG at arch/x86/xen/multicalls.c:103! Jul 31 21:24:15 tomcat01

This is almost ideal for SLP vectorization, except for two problems: 1. We have 4 stores to consecutive locations, but the last element is the constant zero, and not an additional SUB. At the moment we don’t have support for idempotence operations, but this is something that we should add. 2. The values that we are subtracting come from 3 loads. We usually load 4 elements from memory, or

Hi all, I would like to know if LLVM Neon intrinsics are designed to support only 'Legal' types for NEON units. Using llc -march=arm -mcpu=cortex-a9 vmax4.ll -o vmax4.s on following ll code: ; ModuleID = 'vmax.ll' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-n32" target triple =

...4(N2) > > d5(N1) d6(N1) d7(N1) d8(N1) d9(N1) d10(N1) d11(N1) d12(N1) d13(N1) > > d14(N1) d15(N1) d16(N1) d17(N2) d18(N1) d19(N1) d20(N1) . > > > > - RECORD TYPE 'B'. > > - DATA LIST LIST / i1(A1) d21(N1) d22(N1) d23(N1) d24(N1) d25(N1) > > d26(N1) d27(N1) d28(N1) d29(N1) d30(N1) d31(N1) d32(N1) d33(N1) > > d34(N1) d35(N1) d36(N1) d37(N1) d38(A37) d39(N1) d40(N1) . > > > > - RECORD TYPE 'C'. > > - DATA LIST LIST / i2(A1) d41(N1) d42(N1) d43(N1) d44(N1) d45(N1) > > d46(N1) d47(N1) d48(N1) d49(N1) d50(N1) d51(N1) d52(N...