2 Sep
2016
2 Sep
'16
7:11 p.m.
Hi, thanks for the response.
On 26/08/2016, Christiaan Baaij
You mentioned that GHC does name mangling, but I must say I've never seen GHC do this.
I guess this was unclear: our compiler is mangling the names from GHC core, lest any clash with a BlueSpec keyword. We need to find a way to annotate the Haskell source to tell our compiler to not mangle a name.
What GHC does do is inlining and specialisation, which might optimise away your carefully constructed "primitive".
What I do in this case, is simply mark my "primitive" function, your "exposed" BlueSpec functions, as NOINLINE.
Ah, yes, it seems we will need to do this too.