On Sun, 2006-11-19 at 05:57 +0200, [EMAIL PROTECTED] wrote:
> > Errr, LOOP_EXPR doesn't actually exist anymore :)
> > Loops are always lowered to if-then-else and gotos.
>
> That's nice! I'll check on how things are handled now. Is this true for latest
> release, mainline - current gcc trunk, or g
Sorry, but our NetCat (he he) ate part of my previous e-mail. She (yep it's a
she) lives in our mail server...
Here's what was left out...
> > b. Are LOOP_EXPRs decomposable to combinations of if-then-else and gotos?
> It
> > would help for VM (virtual machine) execution of GIMPLE IR. Ideally, a
> a a. Conditional jumps in GIMPLE are not true three-address-code since they
> > specify two (2) branch targets (in their general form). E.g.:
> >
> > if (cond) then
> > goto target1;
> > else
> > goto target2;
> >
> > IMHO, this should be split (or at least made splittable) into:
> >
> > if (
a a. Conditional jumps in GIMPLE are not true three-address-code since they
specify two (2) branch targets (in their general form). E.g.:
if (cond) then
goto target1;
else
goto target2;
IMHO, this should be split (or at least made splittable) into:
if (cond) then
goto target1;
if (!cond)
Hi there
i have went through some of the GIMPLE stuff (mostly went through the GCCSummit
2003 paper). I think i have some reservations on the structure and semantics
of GIMPLE. Most of my compiler experience comes from interactions with the
SUIF2/MachSUIF2 infrastructure ; admittedly Machine-SUIF
