[mercury-users] Re: segfault in hlc.gc when optimise-constructor-last-call is enabled
mikeday at yeslogic.com
Sun Feb 27 13:27:46 AEDT 2011
If the attached bad.m is compiled with rotd-2011-02-21 in hlc.gc with
optimise-constructor-last-call enabled like this:
mmc --grade hlc.gc --make bad --optimise-constructor-last-call
Then the resulting executable will segfault:
*** Mercury runtime: caught segmentation violation ***
cause: address not mapped to object
address involved: (nil)
Any assistance would be very gratefully appreciated, as we do take a
performance hit if we have to disable this optimisation.
Print XML with Prince!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 970 bytes
Desc: not available
More information about the users