From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Thiemo Seufer Cc: binutils@sources.redhat.com Subject: Re: [PATCH] Fix MIPS ELF64 relocation howtos Date: Mon, 27 Aug 2001 14:06:00 -0000 Message-id: <3B8AB66C.4090007@cygnus.com> References: <20010827023751.B301@rembrandt.csv.ica.uni-stuttgart.de> <20010826175030.B2794@lucon.org> <20010827030223.C301@rembrandt.csv.ica.uni-stuttgart.de> <20010827113213.A9485@lucon.org> <20010827204358.C4669@rembrandt.csv.ica.uni-stuttgart.de> <20010827120012.A10036@lucon.org> <3B8AA714.10209@cygnus.com> <20010827224500.G4669@rembrandt.csv.ica.uni-stuttgart.de> X-SW-Source: 2001-08/msg00647.html > > It's "new" in the sense of having a different calling convention > and can make better use of the 64bit chips capabilities. It's > "traditional" since it doesn't do some weird features like > different symbol sorting as it was introduced by SGI when they > introduced NewABI. Ah! In that case could I strongly encourage people to drop the terms ``new'' and ``traditional'' and, instead, give it a name? Hmm, NewTraditional64 (nt64) is probably not a good choice :-) Is it safe for me to assume that a mips64-elf toolchain isn't suddenly going to start producing this as output? Andrew