On Wed, Jan 05, 2011 at 06:06:33PM -0500, Elnatan Reisner wrote:
> Following up on a post from long ago, here is a patch which prints
> #line directives before goto statements and sets the location of
> gotos inserted when an && or || is unfolded to the location of the
> statement within which the
Following up on a post from long ago, here is a patch which prints
#line directives before goto statements and sets the location of gotos
inserted when an && or || is unfolded to the location of the statement
within which the operator resides. (Before, such inserted goto
statements were giv
Hi,
On Tue, Dec 01, 2009 at 06:21:55PM +0100, Mauro Baluda wrote:
> Is it possible to avoid CIL to add goto's when they are not present in
> the original code?
No.
For-loops are converted to while loops, which requires introducing
gotos.
Regards,
--
Gabriel Kerneis
---
Is it possible to avoid CIL to add goto's when they are not present in
the original code?
I don't mind to have code repeated if the only reason for CIL to add
gotos is this
thanks
Mauro
--
Computer science is no more about computers than astronomy is about telescopes
- Edsger W. Dijkstra
---
Is there a reason the defaultCilPrinterClass doesn't print line
directives before gotos? Not printing them makes the line numbers of the
output not quite agree with the original source. For example, CIL
converts:
int main() { goto L; L: return 0; }
into
#line 1 "file.c"
int main(void)
{
{
