[Nasm-devel] machofix branch

[H. P. A. <hp...@zy...>]

I have checked in my code which I believe fixes macho64 into a branch, simply because I think the code still needs some cleanup and a port to 32 bits; ideally the two macho backends ought to be merged.

I also think we should drop the --allow-64-bit option and at most demote it to a warning.  Right now some backends will outright malfunction if presented with 64-bit relocations, but if we can catch that in generic code (throwing an error instead) then we don't have to do surgery to every backend and still be able to generate 64-bit code as long as all the relocations are representable.

For the specific case of  64-bit absolute relocation we could actually emit a 32-bit relocation and zero extend it, on the assumption that only 32-bit addresses will be used.  That ought to be a warning, though.
-- 
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.