From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22121 invoked by alias); 14 Jul 2002 17:43:25 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 22083 invoked from network); 14 Jul 2002 17:43:24 -0000 Received: from unknown (HELO iris1.csv.ica.uni-stuttgart.de) (129.69.118.2) by sources.redhat.com with SMTP; 14 Jul 2002 17:43:24 -0000 Received: from rembrandt.csv.ica.uni-stuttgart.de ([129.69.118.42]) by iris1.csv.ica.uni-stuttgart.de with esmtp (Exim 3.36 #2) id 17TnMA-001CYH-00; Sun, 14 Jul 2002 19:40:26 +0200 Received: from ica2_ts by rembrandt.csv.ica.uni-stuttgart.de with local (Exim 3.35 #1 (Debian)) id 17TnOu-00046Y-00; Sun, 14 Jul 2002 19:43:16 +0200 Date: Sun, 14 Jul 2002 10:53:00 -0000 To: Eric Christopher Cc: Richard Sandiford , gcc-patches@gcc.gnu.org, binutils@sources.redhat.com, macro@ds2.pg.gda.pl Subject: Re: RFC & patch: Rework MIPS command-line handling Message-ID: <20020714174316.GI19894@rembrandt.csv.ica.uni-stuttgart.de> References: <1026499078.25426.27.camel@ghostwheel.cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1026499078.25426.27.camel@ghostwheel.cygnus.com> User-Agent: Mutt/1.4i From: Thiemo Seufer X-SW-Source: 2002-07/txt/msg00295.txt.bz2 Eric Christopher wrote: [snip] > >I'd prefer to select the default ABI at the configure time, from the > >target triplet ideally. E.g. I use a local patch that select the 64 > >ABI as the default for binutils if configuring for mips64*-*-linux*. > >The same is set in the specs file for gcc for this target. I'd prefer this, too. My local patch for mips64*-*-linux* uses n32 as default because n64 is only useful for OS kernels and WRT userland for large memory machines. > This is only particularly convenient for the hosted toolchains, and I > don't think I want to get into the habit of splitting things between > OSes and embedded toolchains. AFAICS this is done in the target specific code, so it is already splitted. [snip] > This is probably only convenient with hosted toolchains. Also, many > people are accustomed to the toolchain deciding ABI for them. Also, the > historical precedent (not always something to look at, but...) of the > SGI compiler switches ABI based on -mipsX switch as well. And then they invented the (undocumented) -mabi switch, I assume because automatic switching didn't work particularily well. > >Well, the intent seems valid (certain sets of options make > >non-conforming files to be generated), but the check is incomplete. > >Note the ABI setting gets propagated to the ELF header of a generated > >file, so both the ABI field and the ABI invalidation code like above > >should probably remain in place. > > Some sort of error checking should be there, that's part of what we get > with Richard's new patch. The old error checking was well.. error prone > and not in any way marginally complete. It was simply a hack to make things a little bit better without breaking backward compatibility. Thiemo