[m-dev.] Trying to add shared objects support for ARM

Sergey Khorev iamphet at nm.ru
Mon Dec 5 23:18:19 AEDT 2005

Thanks for inclusion ARM support into CVS. Currently, I've compiled and tested asm_fast.gc, hlc.gc, asm_fast.gc.tr, asm_fast.gc.tr.debug, asm_fast.gc.tr.decldebug, asm_fast.gc.prof, asm_fast.gc.memprof grades.

The outstanding test failures mentioned in my previous emails had their roots in gcc optimiser bug rather than in Mercury or system I/O quirks!

Insipired with this fact I'm trying to add support for shared libraries. It seems that platform-specific hacks in runtime/mercury_goto.h are not as fearful as they appeared for me at first sight.
At least I can literally translate them to ARM assemly language without much knowledge about it or ELF :) I believe there is a chance this will work after series of attempts.
BUT: comment in runtime/mercury_goto.h states
  (I don't understand the details exactly, this code is
   basically copied from the output of `gcc -fpic -S')

I wonder what file should I compile with -fpic -S to see manipulations with GLOBAL_OFFSET_TABLE? Doesn't this really mean "compile with -fpic and then disassemly"? ;)
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

More information about the developers mailing list