search for: stmt_2

On Thu, Oct 01, 2015 at 07:09:02PM +0300, Roman Kagan wrote: > On Thu, Oct 01, 2015 at 04:22:14PM +0100, Richard W.M. Jones wrote: > > On Thu, Oct 01, 2015 at 06:04:03PM +0300, Roman Kagan wrote: > > > On Mon, Aug 10, 2015 at 06:55:28PM +0300, Roman Kagan wrote: > > > > Libguestfs supports passing an ISO image as a source of virtio windows > > > > drivers

...l the drivers > do get copied into the guest upon conversion. > > So this code does work as intended; being totally clueless in OCaml I'd > appreciate being explained -- how? It's like in C. The following two if statements do different things: if foo then ( stmt_1; stmt_2; ) if foo then stmt_1; stmt_2; The second one runs stmt_2 unconditionally. > > > - Calling String.lowercase is unsafe (because the function is just > > > broken in OCaml) and unnecessary. Just remove it. > > I can't figure out why it's unnecessary...

On Aug 11, 2008, at 2:02 PM, Benedict Gaster wrote: > We would like to develop a code generator using LLVM for a target > language that does not support conditional branches and in fact only > supports structured control flow, eg. If and while. What's the difference between an "if" and a conditional branch? > As far as I can tell that the problem with doing this in

We would like to develop a code generator using LLVM for a target language that does not support conditional branches and in fact only supports structured control flow, eg. If and while. As far as I can tell that the problem with doing this in LLVM today, is that it does not support these high-level constructs and instead all control flow is implemented as branches. It is ³fairly²

...st upon conversion. > > > > So this code does work as intended; being totally clueless in OCaml I'd > > appreciate being explained -- how? > > It's like in C. The following two if statements do different things: > > if foo then ( > stmt_1; > stmt_2; > ) > > if foo then > stmt_1; > stmt_2; > > The second one runs stmt_2 unconditionally. Looks right... The problem is that the statement which runs unconditionally is g#cp source target where, in case the condition evaluates to false, "target" i...

...this does not need to be the case. The paper that I sighted does not use code replication to resolve irreducible control flow but instead introduces a loop construct. For example, consider the following irreducible loop (taken directly from the paper): if(x) goto L2; L1: stmt_1; L2: stmt_2; if(y) goto L1; Using the algorithm described for goto elimination this can be re-written as: goto_L2 = x; do { if (!goto_L2) { goto_L1 = 0; stmt_1; } goto_L2=0; stmt_2; goto_L1=y; } while (goto_L1); In this case the...