| To: | "Maciej W. Rozycki" <macro@linux-mips.org> |
|---|---|
| Subject: | Re: CVS Update@linux-mips.org: linux |
| From: | Thiemo Seufer <ths@networkno.de> |
| Date: | Thu, 7 Jul 2005 14:22:26 +0200 |
| Cc: | Thiemo Seufer <ths@networkno.de>, linux-mips@linux-mips.org |
| In-reply-to: | <Pine.LNX.4.61L.0507071314010.3205@blysk.ds.pg.gda.pl> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20050707091937Z8226163-3678+1737@linux-mips.org> <Pine.LNX.4.61L.0507071227170.3205@blysk.ds.pg.gda.pl> <20050707121235.GV1645@hattusa.textio> <Pine.LNX.4.61L.0507071314010.3205@blysk.ds.pg.gda.pl> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.9i |
Maciej W. Rozycki wrote: > On Thu, 7 Jul 2005, Thiemo Seufer wrote: > > > -mel/-meb aren't documented. > > They are: > > $ gcc -v --help 2>/dev/null | egrep 'mel|meb' > -mel Use little-endian byte order > -meb Use big-endian byte order > > They are not in the info pages, but that should probably be considered an > accidental omission. Is using something that's documented but doesn't > work, to the contrary, any better? Probably not. It's just that I've never seen actual use of -mel/-meb yet. Thiemo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: CVS Update@linux-mips.org: linux, Maciej W. Rozycki |
|---|---|
| Next by Date: | Re: CVS Update@linux-mips.org: linux, Maciej W. Rozycki |
| Previous by Thread: | Re: CVS Update@linux-mips.org: linux, Maciej W. Rozycki |
| Next by Thread: | Re: CVS Update@linux-mips.org: linux, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |