search for: cf80

...random. I noticed that running opt without options on the random file changes the order of references in the predecessors of basic blocks (sample below). Further invocations of opt are idempotent. I don't know of this information is stored in the bytecode file as well. < ; preds = %CF, %CF80, %CF78 > ; preds = %CF80, %CF, %CF78 FWIW, the conflicting section of the bytecode file is likely not a permutation because the byte patterns don't match (some of the btte values of stress-1.bc are not present in stress-2.bc). Thanks for your help :) Sébastien Michelland On 5/24/19 5:3...

...options on the random file changes > the order of references in the predecessors of basic blocks (sample > below). Further invocations of opt are idempotent. > > I don't know of this information is stored in the bytecode file as well. > > < ; preds = %CF, %CF80, %CF78 >  > ; preds = %CF80, %CF, %CF78 > > FWIW, the conflicting section of the bytecode file is likely not a > permutation because the byte patterns don't match (some of the btte > values of stress-1.bc are not present in stress-2.bc). > > Thanks...

Hi LLVM, I'm currently setting up some tools to investigate the influence of the order of optimization passes on the performance of compiled programs -nothing exceptional here. I noticed something inconvenient with opt, namely that splitting a call does not always give the same output: % llvm-stress > stress.ll % opt -dse -verify -dce stress.ll -o stress-1.bc % opt -dse stress.ll |

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB