Date: Tue, 9 Jul 2013 21:04:12 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@freebsd.org> Cc: Andrew Turner <andrew@fubar.geek.nz>, freebsd-arch@freebsd.org Subject: Re: Adding a MACHINE_ARCH note Message-ID: <5F95D699-78E2-493C-ACB7-D26D70FE3D49@bsdimp.com> In-Reply-To: <CAJ-Vmo=iV8BsGriFRgNuP-ZJdQhpmBLhjAkz-nSVRS0HPKSyOQ@mail.gmail.com> References: <20130709090744.0e497e7e@bender.Home> <32F979BD-FB5C-4111-9586-4C5E7C6DFA71@bsdimp.com> <20130709234837.559e3769@bender.Home> <CAJ-Vmo=iV8BsGriFRgNuP-ZJdQhpmBLhjAkz-nSVRS0HPKSyOQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 9, 2013, at 6:40 PM, Adrian Chadd wrote: > Someone pointed out there's dirty people running 32-bit binaries using > the 64-bit intel/amd instruction set. > > Is this also able to represent that? The elf headers represent that. Warner > > -adrian > > On 9 July 2013 15:48, Andrew Turner <andrew@fubar.geek.nz> wrote: >> On Tue, 9 Jul 2013 08:19:46 -0600 >> Warner Losh <imp@bsdimp.com> wrote: >>> I thought that the ELF headers gave us all the data we needed to know >>> how things were built... >> >> It will tell us if it was for e.g. an ARM or MIPS ELF file, but I'm not >> sure how we can tell the difference between an arm and an armv6 ELF. >> >> With armv6 there are a few changes in the userland/kernel >> interface, e.g. reading the thread local storage pointer is different >> such that an armv6 static binary would not run on an ARMv5 core as it >> uses newer instructions. >> >> Andrew >> _______________________________________________ >> freebsd-arch@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arch >> To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5F95D699-78E2-493C-ACB7-D26D70FE3D49>