search for: l81

...gt; Ultimately, I guess this boils down to what exactly the difference is in > intent between O2 and O3, which seems like a never-ending discussion... > The definitions I am working from are here: https://github.com/llvm-project/llvm-project/blob/master/llvm/include/llvm/Passes/PassBuilder.h#L81-L90 I've highlighted the part that makes me think O3 is better here: the code size increases (and thus compile time increases) don't seem to correspond to runtime improvements. > > Hoping you find this useful, > Very. Once again, this kind of data and analysis is awesome. =D &...

...ithub.com/freebsd/freebsd/blob/master/sys/amd64/amd64/elf_machdep.c#L321 But in my case, the kernel objects are created as shared objects. Using shared objects is atypical for amd64, but done for every other architecture except mips: https://github.com/freebsd/freebsd/blob/master/sys/conf/kmod.mk#L81 The comments in the D43383 review suggest that a modern linker should reduce the PLT32 relocations to PC32 for local calls. But I do not see that reduction even when testing this and other examples with lld 10. My understanding is this is due to the shared kernel objects. The relocations are being...

...t levels 4 and 7 on the call stack), and in the inner call (7), a variable, `task`, does not have the correct value. It should be a function, but it isn't; it's either NULL or some other non-function value. That code is here: https://github.com/rstudio/pool/blob/f7e52a3/R/scheduler.R#L79-L81 Note that there's a `force(task)` a couple lines above, which is commented out. If that is uncommented, the test passes, even though calling force() there shouldn't make a difference. Also, calling `format(1)` at that location also causes the test to pass. I've written instructions to...

Hi, I'm interesting in find a pass for loop unrolling in LLVM compiler. I tried opt --loop-unroll --unroll-count=4, but it don't work well. What pass I can used and how? I would also like to know if there is any way to mark the loops that I want them to be unroll Thanks you. -------------- next part -------------- An HTML attachment was scrubbed... URL:

(Apologies if I missed anyone off the To: line. Please add anyone else who is interested, but keep the libguestfs public mailing list) I did some preparatory work on adding the new ‘virt-v2v -o openstack’ output mode. I've put it in a private (non-FFwd) branch here: https://github.com/rwmjones/libguestfs/tree/openstack Most of the work was refactoring virt-v2v so that we have all of the

...ltimately, I guess this boils down to what exactly the difference is in intent between O2 and O3, which seems like a never-ending discussion... > > The definitions I am working from are here: > https://github.com/llvm-project/llvm-project/blob/master/llvm/include/llvm/Passes/PassBuilder.h#L81-L90 <https://github.com/llvm-project/llvm-project/blob/master/llvm/include/llvm/Passes/PassBuilder.h#L81-L90> > > I've highlighted the part that makes me think O3 is better here: the code size increases (and thus compile time increases) don't seem to correspond to runtime impro...

...i32> <i32 undef, i32 2> %I76 = insertelement <2 x i1> %Cmp72, i1 %Sl42, i32 0 %B77 = xor i16 27357, %B28 %PC78 = bitcast i1* %PC to i32* %Sl79 = select i1 %Cmp64, <4 x i16> %Shuff14, <4 x i16> %Shuff7 %Cmp80 = icmp slt <2 x i1> zeroinitializer, %Shuff20 %L81 = load i1, i1* %PC br i1 %L81, label %CF241, label %CF245 CF245: ; preds = %CF245, %CF265 store i1 true, i1* %PC %E82 = extractelement <1 x i32> %Shuff33, i32 0 %Shuff83 = shufflevector <4 x i16> zeroinitializer, <4 x i16> %Shuff...

...call stack), and in the inner call (7), a variable, > `task`, does not have the correct value. It should be a function, but > it isn't; it's either NULL or some other non-function value. > > That code is here: > https://github.com/rstudio/pool/blob/f7e52a3/R/scheduler.R#L79-L81 > Note that there's a `force(task)` a couple lines above, which is > commented out. If that is uncommented, the test passes, even though > calling force() there shouldn't make a difference. Also, calling > `format(1)` at that location also causes the test to pass. > > >...

...deal with the unlocking. See these links for how we do it in libguestfs: https://github.com/libguestfs/libguestfs/blob/50ca24b634f59f1a14fd230aa4893d7408347d76/common/utils/cleanups.h#L27 https://github.com/libguestfs/libguestfs/blob/50ca24b634f59f1a14fd230aa4893d7408347d76/lib/guestfs-internal.h#L81-L87 https://github.com/libguestfs/libguestfs/blob/50ca24b634f59f1a14fd230aa4893d7408347d76/lib/errors.c#L179 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds V...

Hello, I didn't give enough information when I sent an query before, so I'm trying again with a more detailed explanation: In this data set, each patient has a different number of measured variables (they represent tumors, so some people had 2 tumors, some had 5, etc). The problem I have is that often in later cycles for a patient, tumors that were originally measured are now missing (or

...L321 >>>> >>>> But in my case, the kernel objects are created as shared objects. Using shared objects is atypical for amd64, but done for every other architecture except mips: >>>> >>>> https://github.com/freebsd/freebsd/blob/master/sys/conf/kmod.mk#L81 >>>> >>>> The comments in the D43383 review suggest that a modern linker should reduce the PLT32 relocations to PC32 for local calls. But I do not see that reduction even when testing this and other examples with lld 10. My understanding is this is due to the shared kernel...

Thanks for running these Kristof! I'd still like to hear from Apple, and if we can get a few more x86 micro-architectures covered that'd be great, but it looks like -O3 is uncontroversial, and the question is whether this makes sense at O2... To me, it would help a lot to know the actual breakdown of benchmarks such as yours Kristof (as they seem to have more codesize impact than others

...gt; -loop-unroll should be the right pass. There are multiple possible reasons > why the loop is not unrolled and the pass has a bunch of options to > enable/force unrolling for more cases (see > https://github.com/llvm/llvm-project/blob/master/llvm/lib/Transforms/Scalar/LoopUnrollPass.cpp#L81). > > > Passing `-debug` should give you a better idea why the loop is not > unrolled. If you would share the IR, someone might be able to provide > additional insight. > > > I would also like to know if there is any way to mark the loops that I > want them to be unroll &...

I want to make my nbd forwarding plugin fully parallel - but to do that, I first need to make nbdkit itself fully parallel ;) With this series, I was finally able to demonstrate out-of-order responses when using qemu-io (which is great at sending back-to-back requests prior to waiting for responses) coupled with the nbd file plugin (which has a great feature of rdelay and wdelay, to make it

...;I!^^7!pY4x7#eSE$~ zPfUHe;Y+FWR2V+*3{RyYRKA!ON#7Ks3}4>`p3#OcXQ5|xnlF2vXN=)XuJw#Hd`Z(h z;|yO$gJ--U-25|C!{?dqnP~XlneUlo_*^xf$%fEWF~#tu&h%6pzCN=&HAbd7#na^B zzl62IBaVBLrW$a at 3qMUW;H+1Enr^^ZZ~QdFfU`;hRBOOF!vk?=)fsT^hyb1TPzO34 z8xBumq<F-2k9h8J%|y%lh*_xYMZAUeXjPt=ZDeXMJ!RfN0~$8XyHU;bi~`K^j`l81 z^X1lh*Q8~ojP*9AW%(upW at b$CZcX#~>%8;RGSen_SEOZT*LWM at j_KYxhOgfY@4B=s zSB3X*T2 at xIcP=U%2 at RRaW4!ZVLS35Jn3mONJcP5-Cwdp8Wx6W?vy!SHkeN9J!kJpR zcVk*+>Ns!A&J}4{?@aa1hqd1p^<H%W`)5>u7P5cZDBjjN-uUQS#6|mv7I at VdsfkHf zh!z_NaNZ?e(dOkp+;Y;ZF5!|10b0s>CnfxP)+;V~-OJ#0>;smgFgZnCfxbu%...