Mike Stump wrote:
On Aug 12, 2005, at 3:45 PM, Laurent GUERBY wrote:
Isn't it possible to attach some information on a comparison
statement that tells code generation never to never
optimize away this particular comparison even if it
seems to be able to prove it is always true or false?
Cough, hack, ick.
i really think the better hack is one that says
do not propagate type range info through a
conversion, or perhaps says "drop any information you think
you have deduced about the range of this expression, if
either
a) that info comes from type range analysis
or
b) u do not know where it came from
