<html>
<head>
<base href="http://bugzilla.gdcproject.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - cc1d locks up when specifying function instead of function pointer in an array"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=178#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - cc1d locks up when specifying function instead of function pointer in an array"
href="http://bugzilla.gdcproject.org/show_bug.cgi?id=178">bug 178</a>
from <span class="vcard"><a class="email" href="mailto:jens-bugzilla@gpio.dk" title="Jens Bauer <jens-bugzilla@gpio.dk>"> <span class="fn">Jens Bauer</span></a>
</span></b>
<pre>(In reply to Ketmar Dark from <a href="show_bug.cgi?id=178#c5">comment #5</a>)
<span class="quote">> private immutable ubyte[256] tblParity = genParityTable();
>
> it's vital to understand that `tblParity` is initialized in COMPILE time,
> there is no runtime function calls.</span >
I agree; CTFE is a good feature, indeed.
Does this happen only for immutable assignments ?
If so, then the problem is not so big, but it still is nasty, when the compiler
locks up.
Detection could probably be tricky. I would expect that even if checking the
condition given to while() could fail, so that when there's in fact no lock-up,
it would happen as well.
And a naive 32-bit loop-counter would probably not do well either.
Recognizing a while(constant){ ... } would of course help.
I think that it all boils down to if there's a branch-back without any kind of
conditional exit instruction in the generated code, it would work quite well
(but would probably not be completely foolproof).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>