Re: [PATCH] OSX: Mach-O object file output
- From: Mike Pall <mike-1210@xxxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Mon, 29 Oct 2012 17:55:57 +0100
Adam Strzelecki wrote:
> (1) iOS & clang makes distinction for ARM CPU subtypes: armv6,
> armv7, armv7s
>
> Unfortunately CPU_SUBTYPE_ARM_ALL is deprecated. Even .o file is
> __DATA only 32-bit segment, we need to produce .o marked for
> specific subtype or linker will complain. Right now we can
> specify "-a arm", but we need to be more specific i.e. giving
> "-a armv7".
Can't you produce an armv6 file and link that against any higher
architecture level, too?
> (2) If we are about to support FAT mach-o .o files (containing
> multiple platforms), which I think we should, we need again to
> line up with "clang" or "gcc" that produce FAT .o files when you
> specify multiple "-arch" options.
Well, but it doesn't work to put the 32 bit and 64 bit VM together
into a FAT object file, anyway. So why bother doing this for the
bytecode?
--Mike
Other related posts:
