Date: Wed, 2 Jun 2010 08:42:49 -0400 From: John Baldwin <jhb@freebsd.org> To: Juli Mallett <jmallett@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r208737 - in head: contrib/binutils/bfd contrib/binutils/gas/config contrib/binutils/include/elf contrib/binutils/include/opcode contrib/binutils/opcodes contrib/gcc/config contrib/gcc/... Message-ID: <201006020842.49509.jhb@freebsd.org> In-Reply-To: <201006021106.o52B63PZ035362@svn.freebsd.org> References: <201006021106.o52B63PZ035362@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 02 June 2010 7:06:03 am Juli Mallett wrote: > Author: jmallett > Date: Wed Jun 2 11:06:03 2010 > New Revision: 208737 > URL: http://svn.freebsd.org/changeset/base/208737 > > Log: > Add/improve mips64r2, Octeon, n32 and n64 support in the toolchain. > > o) Fix our GCC spec to define __mips64 for 64-bit targets, not __mips64__, the > former being what libgcc, etc., check and the latter seemingly being a > misspelling of a hand merge from a Linux spec. I wonder if it would be useful to define both? The macros we check for architecture-specific code for other architectures all have both leading and trailing underscores (e.g. __i386__, __amd64__, etc.). Being able to use __mips64__ instead of __mips64 for that in kernel sources, etc. would be more consistent. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006020842.49509.jhb>