Date: Sat, 16 Dec 2017 08:00:13 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm@freebsd.org Subject: as(1) for aarch64 (Was: Re: gcc for aarch64) Message-ID: <20171216080013.GA43041@FreeBSD.org> In-Reply-To: <CANCZdfoBy=x6d2n3tY8Kv=f-xJutQwNygZ3ZmZ1M2iXQTYB7zQ@mail.gmail.com> References: <5eb49766-e5af-d89f-b4f6-a0d655a3859a@bsd.com.br> <CANCZdfoBy=x6d2n3tY8Kv=f-xJutQwNygZ3ZmZ1M2iXQTYB7zQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 29, 2017 at 12:22:02PM -0600, Warner Losh wrote:
> The in-tree gcc compiler doesn't have any aarch64 support. Out of tree
> ones should be supported though.
OK, so that would explain why there is no /usr/bin/as on our ref-aarch64
boxes in the cluster.
> Most developers use clang on aarch64
So does it come with assembler, is it GNU-compatible? (I was told it
does: s/${AS} ${ASFLAGS}/${CC} -Wa,${ASFLAGS:ts,}/) If yes, why there
is no wrapper installed as /usr/bin/as?
Or it cannot be used as a drop-in replacement and users that want to
call as(1) directly should install `devel/binutils' port? Thanks,
./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171216080013.GA43041>