| To: | "Fu, He Wei PSE NKG" <hewei.fu@siemens.com> |
|---|---|
| Subject: | Re: The difference between mips*-gnu and mips*-linux when configure tool-chain |
| From: | Thiemo Seufer <ths@networkno.de> |
| Date: | Tue, 5 Dec 2006 12:43:56 +0000 |
| Cc: | Daniel Jacobowitz <dan@debian.org>, linux-mips@linux-mips.org |
| In-reply-to: | <96E7D5519FC3D741BEE27AB88C7387970167840A@PEKW934A.cn001.siemens.net> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20061203170514.GA11258@nevyn.them.org> <96E7D5519FC3D741BEE27AB88C7387970167840A@PEKW934A.cn001.siemens.net> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
Fu, He Wei PSE NKG wrote: > Thanks, sorry for I missed the mips*-elf for mips*-gnu. > > I think that for ld,the difference between mips*-elf and mips*-linux > produces only some minor impact on the default ld script, for the > behavior of ld itself, it has not serious impact.Is it my understanding > correct? > > But for bfd, does the difference of these two config-choice have impact > on the behavior of two different bfd-target? . For both cases the resulting object file layout is different. mips*-elf uses SGI-style, mips*-linux uses "traditional" style. I expect the "traditional" format to get better long-term maintenance. For a stand-alone bootloader both do for now, but I would prefer mips*-linux since it eliminates the need for one extra compiler when building a Linux environment. Thiemo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] pte_offset(dir,addr): parenthesis fix, Franck Bui-Huu |
|---|---|
| Next by Date: | [PATCH] genirq: use name instead of typename, Atsushi Nemoto |
| Previous by Thread: | RE: The difference between mips*-gnu and mips*-linux when configure tool-chain, Fu, He Wei PSE NKG |
| Next by Thread: | [PATCH] fix 64-bit build, Atsushi Nemoto |
| Indexes: | [Date] [Thread] [Top] [All Lists] |