<HTML>
<style> BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }</style>Aah cool. Thanks for that tip. Hmmm... I see "riot" in the flags... I think it's going to be a riot with the errors found!<br>
<div><br>
</div><div>Gareth aka. Kit<br>
</div> <br>
<br>
<span style="font-weight: bold;">On Mon 14/01/19 18:17 , Pierre Muller pierre@freepascal.org sent:<br>
</span><blockquote style="BORDER-LEFT: #F5F5F5 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">Hi all,
<br>
<br>
<br>
Le 14/01/2019 à 15:01, J. Gareth Moreton a écrit :
<br>
<span style="color: rgb(102, 102, 102);">> Hi everyone,
</span><br>
<span style="color: rgb(102, 102, 102);">>
</span><br>
<span style="color: rgb(102, 102, 102);">> I apologise I didn't properly test my case block improvements, especially where optimising for size is concerned. As someone who has worked in SQA, I should have known better.
</span><br>
<span style="color: rgb(102, 102, 102);">>
</span><br>
<span style="color: rgb(102, 102, 102);">> I've also spotted a potential overflow condition (in some situations, max_dist can become negative) - this is thankfully disguised, but I would like to properly trap it and handle it cleanly and safely.
</span><br>
<br>
You should try to add
<br>
-CriotR to OPT when cycliing the compiler,
<br>
as it might find the overfows for you...
<br>
and even also do
<br>
make fullcycle OPT="-n -CriotR -gl"
<br>
as testing the change for 16 bit address
<br>
CPU can also reveal more range checking/overflow exceptions.
<br>
<br>
Pierre
<br>
<br>
_______________________________________________
<br>
fpc-devel maillist - <a href="mailto:fpc-devel@lists.freepascal.org">fpc-devel@lists.freepascal.org</a>
<br>
<a target="_blank" href="<a href="http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</a>"><span style="color: red;">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel</span></a>
<br>
<br>
<br>
</blockquote></HTML>