Mercury Bugs - mercury
View Issue Details
0000515mercuryBugpublic2020-07-31 01:342020-10-16 07:06
Assigned Tozs 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000515: Library not building in deep profiling grades with rotd-2020-07-26
DescriptionCompilation of the the standard library in grade asm_fast.gc.profdeep.stseg with rotd-2020-07-26 onwards results in:

../scripts/mgnuc --grade asm_fast.gc.profdeep.stseg -- -c exception.c -o exception.o
In file included from exception.m:2101:0:
../runtime/mercury_exception_catch_body.h: In function ‘hand_written_exception_module’:
../runtime/mercury_exception_catch_body.h:61:5: error: ‘mercury__profiling_builtin__non_call_port_code_sr_5_0’ undeclared (first use in this function)
../runtime/mercury_exception_catch_body.h:61:5: note: each undeclared identifier is reported only once for each function it appears in
../runtime/mercury_exception_catch_body.h:64:5: error: ‘mercury__profiling_builtin__prepare_for_ho_call_2_0’ undeclared (first use in this function)
../runtime/mercury_exception_catch_body.h:82:5: error: ‘mercury__profiling_builtin__non_exit_port_code_sr_3_0’ undeclared (first use in this function)
In file included from exception.m:2161:0:
../runtime/mercury_exception_catch_body.h:99:5: error: ‘mercury__profiling_builtin__non_redo_port_code_sr_2_0’ undeclared (first use in this function)
../runtime/mercury_exception_catch_body.h:115:5: error: ‘mercury__profiling_builtin__non_fail_port_code_sr_3_0’ undeclared (first use in this function)
exception.c: At top level:

This is occurring on (Also, checked on my Linux machine with GCC 4.8)
TagsNo tags attached.
Attached Files? PATCH.2020_07_31_exception (1,036) 2020-07-31 14:27

2020-07-31 14:27   
I have fix for the linking issue (attached). However, a bootstrap in the deep
profiling grade now gets a SIGSEGV when making the stage 3 dependencies,
even when if I undo the commit that fixed Mantis bug 514 (commit c5b35aca...),
which was the previous change that directly affected deep profiling.
So this needs further investigation.
2020-10-16 07:06   
The fix was committed 2020 aug 1.

Issue History
2020-07-31 01:34juliensfNew Issue
2020-07-31 14:27zsFile Added: PATCH.2020_07_31_exception
2020-07-31 14:27zsNote Added: 0001101
2020-07-31 14:27zsAssigned To => zs
2020-07-31 14:27zsStatusnew => assigned
2020-10-16 07:06zsStatusassigned => resolved
2020-10-16 07:06zsResolutionopen => fixed
2020-10-16 07:06zsNote Added: 0001119