Re: LOOP_EXPR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Dec 28, 2004, at 8:29 AM, Daniel Berlin wrote:

On Tue, 2004-12-28 at 21:42 +0530, Virender Kashyap wrote:
Hi,
I am working on a a particular optimization in GCC and intend to use
GIMPLE for this. I have some doubt about the LOOP_EXPR as given in grammar
of GIMPLE. The documentation mentions a separare expresssion called
LOOP_EXPR to denote loops( as infinite while loops).

The docs i have say " @node Loops @subsubsection Loops @cindex Loops

At one time loops were expressed in GIMPLE using @code{LOOP_EXPR}, but
now they are lowered to explicit gotos.
"

I see following in c-tree.texi.

@item LOOP_EXPR
These nodes represent ``infinite'' loops.  The @code{LOOP_EXPR_BODY}
represents the body of the loop.  It should be executed forever, unless
an @code{EXIT_EXPR} is encountered.

@item EXIT_EXPR
These nodes represent conditional exits from the nearest enclosing
@code{LOOP_EXPR}.  The single operand is the condition; if it is
nonzero, then the loop should be exited.  An @code{EXIT_EXPR} will only
appear within a @code{LOOP_EXPR}.

-
Devang


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux