[m-dev.] MLDS backend generates strange names on reuse branch

[Fergus Henderson]

On 09-Mar-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> Any ideas where a declaration like this would be generated?
> 
> void MR_CALL globals__f_114_101_117_115_101_95_95_112_114_101_100_95_95_84_121_1
> 12_101_83_112_101_99_79_102_95_95_112_114_101_100_95_111_114_95_102_117_110_99_9
> 5_95_115_101_108_101_99_116_95_50_95_95_91_75_32_61_32_118_97_114_40_86_95_50_41
> _93_95_95_48_95_95_48_4_p_0(

It's probably something to do with
<predicate 'reuse:pred:select_2'/3 mode 0 (type specialized [K = var(V_2)])>.
The names are generated by llds_out__name_mangle.

We really ought to implement demangling for the MLDS back-end.

But in the mean time, the work-around is to pull out the big long
`f_<iii>_<jjj>_<kk>_<lll>...<zzz>' string, insert `mercury__' at the front and
append `_1_0' at the end, and then pipe it through mdemangle.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------