Hi Jean-Claude,
thank you for your quick response.
and for ARM would probably be named ffi_arm.d. But that file still has to be written since the port of MKCL on ARM has not been done yet.
I see:-)
On my side, I am currently stuck deep in a large rewrite of the CLOS code of MKCL (with dramatic memory consumption reduction being accomplished) that is nearly completion and that will be part of 1.2.0. The second consideration related to what you point is that the entire FFI interface of MKCL is currently being redone for 1.2.0 and the functions mentioned here above are at various levels of redesign.
Ok, good luck!
That being said, the nearly tragic part of this is that the code you hit on is useful only to provide FFI support to interpreted code, compiled-to-C code does not use it. That part could in fact be stubbed out without much of a loss.
There don't seem to be a configure flag to turn this ffi off. Is there some other way to turn it off?
On the other hand, if your ARM assembler skills and ARM ABI knowledge is up to it you could give a try at writing that ffi_arm.d file, at least as a first draft.
Unfortunatelly, I won't be able to find time to work on this.
BTW, I should push out the door a MKCL 1.1.10 any time now as a bug fix consolidation release. And be aware that the real action is on the 1.2.0 side.
Great, thank you very much!
Tomas