From: Daniel Jacobowitz <drow@false.org>
To: Eric Christopher <echristo@apple.com>
Cc: Chao-ying Fu <fu@mips.com>, Thiemo Seufer <ths@networkno.de>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"Thekkath, Radhika" <radhika@mips.com>,
binutils@sourceware.org
Subject: Re: [patch] GAS supports for MIPS32 MT ASE
Date: Tue, 30 Aug 2005 23:01:00 -0000 [thread overview]
Message-ID: <20050830230024.GA18203@nevyn.them.org> (raw)
In-Reply-To: <F7B73813-E028-4F4F-B025-CC7AFE54EDAD@apple.com>
On Tue, Aug 30, 2005 at 03:56:50PM -0700, Eric Christopher wrote:
>
> On Aug 30, 2005, at 3:53 PM, Chao-ying Fu wrote:
>
> > Ok. I will use -mmt/-mno-mt.
> >But, not all GAS options have the same style.
> >Ex, -mips16/-no-mips16, -mips3d/-no-mips3d
> >Should the options be -mmips16/-mno-mips16 and
> >-mmips3d/-mno-mips3d?
>
> Those are historical (with the exception of the mips3d stuff), and in
> general we should use -m<option>.
>
> I don't think this justifies being a special case, unless you wanted
> to name it -mips-mt.
... please don't. The other options should be fixed and only
compatibility aliases kept, IMO.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-08-30 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 22:05 Chao-ying Fu
2005-08-29 9:55 ` Maciej W. Rozycki
2005-08-29 23:23 ` Chao-ying Fu
2005-08-29 23:41 ` Thiemo Seufer
2005-08-30 22:54 ` Chao-ying Fu
2005-08-30 22:57 ` Eric Christopher
2005-08-30 23:01 ` Daniel Jacobowitz [this message]
2005-08-31 0:25 ` Eric Christopher
2005-08-31 0:49 ` Chao-ying Fu
2005-09-02 12:15 ` Thiemo Seufer
2005-09-02 15:43 ` Eric Christopher
2005-09-05 6:56 ` Chao-ying Fu
2005-09-05 22:33 ` Thiemo Seufer
2005-09-06 16:19 ` Eric Christopher
2005-09-06 21:51 ` Chao-ying Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050830230024.GA18203@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sourceware.org \
--cc=echristo@apple.com \
--cc=fu@mips.com \
--cc=macro@linux-mips.org \
--cc=radhika@mips.com \
--cc=ths@networkno.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).