Closed zyz9740 closed 7 months ago
Hi,
here the problem I see is triggered by Assertion RHS.U.VAL != 0 && "Divide by zero?"
while the code g / e
is visited as part of the PartialInterpreter.
e
in this case will be 0, so it seems the check is right, and I expect it should be a matter of hoisting that check into visitOuter, but I will need to do also a review of other similar cases.
Cannot reproduce
This case has a long-term compilation in O0, works well in O1 and O2, crashes and reports "Floating point exception" on O3. You can have a try.