[mercury-users] try_io on x86-64

Julien Fischer juliensf at csse.unimelb.edu.au
Sat Oct 10 21:03:35 AEDT 2009


On Sat, 10 Oct 2009, Michael Day wrote:

>> This was with rotd-2009-10-0{8,9}.
> I'm afraid I've reproduced the problem:
> - rotd-2009-10-08
> - x86_64-unknown-linux-gnu, gcc 3.4
> - --use-subdirs --make -O3 --intermodule-optimisation
>> The only problem I can report is that you can no longer use "try" as a
>> module name; otherwise everything worked.
> Yes, I had to rename the module. But I still get the bug:
> $ mmc --use-subdirs --make try2 --intermodule-optimisation -O3
> Making Mercury/int3s/try2.int3
> Making Mercury/ints/try2.int
> Making Mercury/opts/try2.opt
> Making Mercury/cs/try2.c
> Making Mercury/os/try2.o
> Making try2
> ** Error making `try2'.
> Mercury/os/try2.o:(.rodata+0x310): undefined reference to `<predicate 
> 'exception.wrap_success_or_failure'/2 mode 0>'
> collect2: ld returned 1 exit status
> IMPORTANT NOTE: I only get this bug after fully bootstrapping the compiler. 
> The first install of the compiler builds it fine, only the second rebuild of 
> the compiler with unboxed floats and 3 tag bits has problems with try_io.

The x86-64 machine I tested on was using those settings.

mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list