| To: | Alexander Voropay <a.voropay@vmb-service.ru> |
|---|---|
| Subject: | Re: MS VC++ compiler / MIPS |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 15 Jul 2004 02:24:54 +0200 |
| Cc: | "'Kevin D. Kissell'" <kevink@mips.com>, linux-mips@linux-mips.org |
| In-reply-to: | <07f501c469c8$85f86240$0200000a@ALEC> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <003001c469b4$3b5ae960$10eca8c0@grendel> <07f501c469c8$85f86240$0200000a@ALEC> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Wed, Jul 14, 2004 at 09:32:23PM +0400, Alexander Voropay wrote: > MSVC/MIPS supports 2 calling conventions (/Gd __cdecl calling > convention; > /Gr __fastcall calling convention) but I can't grok a difference. Probably more argument registers etc. I'd expect something along the NABI callign conventions. > > and certainly the assembler directives will be different from those > assumed by the Linux sources. > > Yes. > > It sems, it is impossible to build a full Linux toolcain at the MSVC > base. The MS linker > (LINK.EXE) is weak (comparing to `ld` monster) and can produce only COFF > .EXE (a.out) > MIPS executables. PECOFF, Microsoft's ECOFF variant which basically is ECOFF plus an MSDOS executable header. Yes, we all run MSDOS on our MIPS boxes so that's and important feature ;-) Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: Strange, strange occurence, Michael Uhler |
|---|---|
| Next by Date: | Re: MS VC++ compiler / MIPS, Ralf Baechle |
| Previous by Thread: | RE: MS VC++ compiler / MIPS, Alexander Voropay |
| Next by Thread: | Re: MS VC++ compiler / MIPS, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |