similar to: [LLVMdev] Code generators (both llvmc and Jit) get stuck when dealing circular CFG

In https://bugs.llvm.org/show_bug.cgi?id=38011 (see also https://reviews.llvm.org/D48721) a problem was revealed related to llvm.loop metadata. The fault was that clang added the !llvm.loop metadata to branches outside of the loop (not only the loop latch). That was not handled properly by some opt passes (simplifying cfg) since it ended up merging branch instructions with different !llvm.loop

Tobias, I am working on one very well hidden issue with Polly loop structure. Here is a brief description. In polly::createLoop() we create something like this (topology is important): polly.start: ; preds = %polly.split_new_and_old ... <some code> br label %polly.loop_header polly.loop_after: ; preds =

Le lundi 23 juin 2008 ? 21:16 +0530, John Kennedy a ?crit : > Salut! bonjour > I have an iBall Nirantar UPS-630 UPS > (http://iball.co.in/inner/show_product_details2.asp?catid=25) and am > interested in hooking it up to my Ubuntu box. Problem - it only comes > with WinPower Windows driver... Alas I search for it's compatibility... > > I send you this message as this

Le lundi 23 juin 2008 ? 21:16 +0530, John Kennedy a ?crit : > Salut! bonjour > I have an iBall Nirantar UPS-630 UPS > (http://iball.co.in/inner/show_product_details2.asp?catid=25) and am > interested in hooking it up to my Ubuntu box. Problem - it only comes > with WinPower Windows driver... Alas I search for it's compatibility... > > I send you this message as this

Is there any chance of replacing/extending the GEP instruction? As noted in the GEP FAQ, GEPs don't support variable-length arrays; when the front ends have to support VLAs, they linearize the subscript expressions, throwing away information. The FAQ suggests that folks interested in writing an analysis that understands array indices (I'm thinking of dependence analysis) should be