Bug 1696 – for(;;) in CTFE segfaults compiler

Seems it's not checking for an empty iteration clause. Putting _anything_ in there, eg for(;;null) stops the segfault. --------- int a() { bool b = false; for (;;) { if (b) return 0; b = true; } } const c = a();

[email protected] wrote: > http://d.puremagic.com/issues/show_bug.cgi?id=1696 > > Summary: for(;;) in CTFE segfaults compiler > Product: D > Version: 1.023 > Platform: PC > OS/Version: Windows > Status: NEW > Severity: normal > Priority: P2 > Component: DMD > AssignedTo: [email protected] > ReportedBy: [email protected] > > > Seems it's not checking for an empty iteration clause. > Putting _anything_ in there, eg for(;;null) stops the segfault. > --------- > int a() > { > bool b = false; > for (;;) { > if (b) return 0; > b = true; > } > } > > const c = a(); > > What if there is a break somewhere in the empty for? The compiler can't know that the function will end it's execution. I think it would be weird if the compiler didn't hang up or segfault on this.

Ary, what do you mean by this? And please don't quote the entire message posted to the newsgroup when replying. It's bad enough on any newsgroup, and when it clutters up Bugzilla, it's even worse.

Sorry, I meant nothing. I was very drowsy I guess.

*** This bug has been marked as a duplicate of 1072 ***