Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Alexander Voropay <a.voropay@vmb-service.ru>
Cc: "'Kevin D. Kissell'" <kevink@mips.com>, linux-mips@linux-mips.org
Subject: Re: MS VC++ compiler / MIPS
Date: Thu, 15 Jul 2004 02:24:54 +0200	[thread overview]
Message-ID: <20040715002454.GA25279@linux-mips.org> (raw)
In-Reply-To: <07f501c469c8$85f86240$0200000a@ALEC>

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

  parent reply	other threads:[~2004-07-15  0:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 13:53 MS VC++ compiler / MIPS Alexander Voropay
2004-07-14 13:53 ` Alexander Voropay
2004-07-14 14:05 ` H.Heinold
2004-07-14 14:10 ` Geert Uytterhoeven
2004-07-14 15:07 ` Kevin D. Kissell
2004-07-14 15:07   ` Kevin D. Kissell
2004-07-14 17:32   ` Alexander Voropay
2004-07-14 17:32     ` Alexander Voropay
2004-07-15  0:24     ` Ralf Baechle [this message]
2004-07-15  0:39   ` Ralf Baechle

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=20040715002454.GA25279@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=a.voropay@vmb-service.ru \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    /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