search for: 32b

...> > > Another problem was that only the first line of the manifest file was > > actually processed. > > Can you please provide an example of manifest file with more than one > line? A real-life example, I mean. > Sure, this is from OVA created by VMware: $ cat 2003-32b.mf SHA1(2003-32b.ovf)= 7c8e2cfebb540c4fa86df8413604408359b35cd9 SHA1(2003-32b-disk1.vmdk)= fef670f077ba7df83d35d8849f666d399f355bb5 If there are multiple disks in the VM there will be one line for each disk. Tomas -- Tomáš Golembiovský <tgolembi@redhat.com>

...e only exists due to this identity copy in %bb.1, which is removed. When the copy is erased and the interval is updated (https://github.com/llvm/llvm-project/blob/523cc097fdafa1bb60373dcc70df7dfd31551f56/llvm/lib/CodeGen/RegisterCoalescer.cpp#L1871), the new live interval looks like this: %0 [16r,32B:2)[32B,96r:0)[96r,128B:1) 0 at 32B-phi 1 at 96r 2 at 16r L0000000000000003 [32B,80B:0) 0 at 32B-phi // sub0 This remaining [32B,80B:0) across %bb.1 is a fake phi-only segment. If I freshly recompute LiveIntervals, the subrange is empty as it should be. The verifier doesn't care about this,...

Yeah, the alternative is to do movabs and then test, which is doable but I’m not sure if it’s worth it (surely BT + risk of flags merging penalty has to be better than two ops, one of which is ~9-10 bytes). Fiona > On Jan 22, 2015, at 2:59 PM, Chris Sears <chris.sears at gmail.com> wrote: > > My bad on that. So that's what the comment meant. > That means BT is pretty much

...omUs/guests using virt-install and/or virt-manager on CentOS 5.3 Xen x86_64 dom0/host. It doesn't work. The guest kernel crashes early and the graphical VNC console newer shows up. Installing x86_64 domU on x86_64 dom0 work well. 32-on-32 works aswell. So it's a 32-on-64 bug. CentOS 5.3 32b guest on x86_64 host works though, most probably because it uses the "original" Xenlinux patchset. I found the upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=467698 This problem will be fixed in upcoming RHEL 5.4, and it's also fixed in the latest el5 test kernel-xen (-15...

On Thu Jan 22 2015 at 3:32:53 PM Chris Sears <chris.sears at gmail.com> wrote: > The status quo is: > > a) 40b REX+BT instruction for the 64b case > b) 48b TEST for the 32b case > c) unless it's small TEST > > > You are currently paying a 16b penalty for TEST vs BT in the 32b case. > That may be worth testing the -Os flag. > You'll want -Oz here, Os isn't supposed to affect the runtime as much as this is going to. -eric -------------- n...

...be really possible without too much painfull work ? Does any body have ideas of how to do that and about benchmarks for mips and memory on embedded platform ? What I see for straight data format assignement : Standard C C54x Compiler char 8b 16b short,ushort 16b 16b int,uint 32b 16b long,ulong 32b 32b float 32b 32b double 64b 32b long double 64b 32b So I will have to do int(std C) -> float ( DSP C) double(std C) -> float ( DSP C) or even create special routines to handle bigger data ( 64 b). For benchmarking, I have seen: > Actually, we have a integeri...

Has anyone been able to boot a fully virtualized (Intel VT) 32bit guest on XEN32 unstable? I''m trying to setup a nightly test environment for this configuration and XEN32 nosmp hangs when launching a 32bit guest, and XEN32 smp gets a double fault launching a 32bit guest. It happens pretty early as the SDL window doesn''t come up. I trie...

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from:

Folks, Xen 3.4.2 is the latest maintenance release in the 3.4 stable branch. There are a range of bug fixes since 3.4.1, and we recommend users to upgrade. The source repository can be downloaded from: http://xenbits.xensource.com/xen-3.4-testing.hg The release is tagged ''RELEASE-3.4.2''. Alternatively source tarballs can be downloaded from:

...egister allocator, the code is identical when compiling with and without -g (with the exception of " DBG_VALUE" instructions). The only difference I can see is the value assigned to the slot index for each instruction. As an example, without -g a snippet of a basic block looks like this: 32B %vreg29<def> = LDImm 1; REG1:%vreg29 36B %vreg44<def> = LDImm 1103515245; REG1:%vreg44 40B %vreg143:vsub32_1<def,read-undef> = LDImm 0; REG2:%vreg143 44B %vreg68<def> = LDImm 12345; REG1:%vreg68 64B %vreg143:vsub32_0<def> = COPY %vreg...

I don't think C has a way to express 32b x 32b -> 64b multiply, even though there is (on x86 anyway) a hardware instruction that does it. The type of your expression (x * y) is still uint32_t. The implicit type coercion up to uint64_t as part of the return statement doesn't change this. On Jan 13, 2008, at 10:29 PM, Zhou S...

...anks Yunfeng >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ed Smith >Sent: 2006年4月28日 4:56 >To: xen-devel@lists.xensource.com >Subject: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston >XEN32 unstable > >Has anyone been able to boot a fully virtualized (Intel VT) 32bit guest >on XEN32 unstable? I''m trying to setup a nightly test environment for >this configuration and XEN32 nosmp hangs when launching a 32bit guest, >and XEN32 smp gets a double...

...il.com <mailto:echristo at gmail.com>> wrote: > > > On Thu Jan 22 2015 at 3:32:53 PM Chris Sears <chris.sears at gmail.com <mailto:chris.sears at gmail.com>> wrote: > The status quo is: > > a) 40b REX+BT instruction for the 64b case > b) 48b TEST for the 32b case > c) unless it's small TEST > > You are currently paying a 16b penalty for TEST vs BT in the 32b case. > That may be worth testing the -Os flag. > > You'll want -Oz here, Os isn't supposed to affect the runtime as much as this is going to. > > -eric >...

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier. - This prob...

Hi, Here is C function: uint64_t mul(uint32_t x, uint32_t y) { return x * y; } current llvm-gcc-4.0 with -O3 will compile it to: define i64 @mul(i32 %x, i32 %y) nounwind { entry: %tmp3 = mul i32 %y, %x ; <i32> [#uses=1] %tmp34 = zext i32 %tmp3 to i64 ; <i64> [#uses=1] ret i64 %tmp34 } This seems incorrect. I think it should extend %x, %y to i64 first and

OK try it now - I checked in a few more fixes. On Tue, Feb 22, 2011 at 8:29 AM, Chuck Zhao <czhao at eecg.toronto.edu> wrote: > I still can't build LLBrowse on my Debian5-i386 machine today, > The following is a full build console output. > I am using LLVM-2.8 release build, with needed wxWidgets and CMake. > > Thank you > > Chuck > > sideshow.eecg>time

...egating, iff the shift amount is defined to be modulo and the machine is two's complement. I'm a bit worried that while modulo is the Obviously Right Thing for rotates, the situation is less clear for general funnel shifts. I looked over some of the ISAs I have docs at hand for: - x86 (32b/64b variants) has SHRD/SHLD, so both right and left variants. Count is modulo (mod 32 for 32b instruction variants, mod 64 for 64b instruction variants). As of BMI2, we also get RORX (non-flag-setting ROR) but no ROLX. - ARM AArch64 has EXTR, which is a right funnel shift, but shift distances...

...w <fi#-2>, 0; mem:LD4[FixedStack-2] IntRegs:%vreg31 24B %vreg26<def> = COPY %R0<kill>; IntRegs:%vreg26 28B %vreg106<def> = TFRI 16777216; IntRegs:%vreg106<<<<<<<<<<<<<<<<<<<<<<<<<<< CurrentTop 32B %vreg29<def> = COPY %D2<kill>; DoubleRegs:%vreg29 48B %vreg28<def> = COPY %D1<kill>; DoubleRegs:%vreg28 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Needs to move ab...

...his relatively high level. At the machine level it looks like it is the register coalescer that is duplicating the constant. It transforms 0B BB#0: derived from LLVM BB %entry 16B %vreg0<def> = MOV64rm %RIP, 1, %noreg, <ga:@val>[TF=5], %noreg; mem:LD8[GOT] GR64:%vreg0 32B %vreg1<def> = MOV64rm %RIP, 1, %noreg, <ga:@p>[TF=5], %noreg; mem:LD8[GOT] GR64:%vreg1 48B MOV64mr %vreg1, 1, %noreg, 0, %noreg, %vreg0; mem:ST8[@p](tbaa=!"any pointer") GR64:%vreg1,%vreg0 64B %vreg2<def> = MOV64ri 12345123400; GR64:%v...

...the first line of the manifest file was > > > actually processed. > > > > Can you please provide an example of manifest file with more than one > > line? A real-life example, I mean. > > > > Sure, this is from OVA created by VMware: > > $ cat 2003-32b.mf > SHA1(2003-32b.ovf)= 7c8e2cfebb540c4fa86df8413604408359b35cd9 > SHA1(2003-32b-disk1.vmdk)= fef670f077ba7df83d35d8849f666d399f355bb5 > > > If there are multiple disks in the VM there will be one line for each > disk. This is correct, but ... This code works currently. How?...