From: "Kevin D. Kissell" <kevink@mips.com>
To: <a.voropay@vmb-service.ru>, <linux-mips@linux-mips.org>
Subject: Re: MS VC++ compiler / MIPS
Date: Wed, 14 Jul 2004 17:07:06 +0200 [thread overview]
Message-ID: <003001c469b4$3b5ae960$10eca8c0@grendel> (raw)
In-Reply-To: 07d301c469a9$e708f550$0200000a@ALEC
If I recall correctly, the MS compiler uses a subltly different
calling convention/ABI than the "o32" gcc conventions assumed
by MIPS Linux, and certainly the assembler directives will be
different from those assumed by the Linux sources. It *might*
be possible to hack up a MIPS Linux kernel source tree to
build with the MS tool kit, but it would be a lot of work,
some of it subtle.
Regards,
Kevin K.
WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: a.voropay@vmb-service.ru, linux-mips@linux-mips.org
Subject: Re: MS VC++ compiler / MIPS
Date: Wed, 14 Jul 2004 17:07:06 +0200 [thread overview]
Message-ID: <003001c469b4$3b5ae960$10eca8c0@grendel> (raw)
Message-ID: <20040714150706.V1G6vdIoK85CdaDueo1RY9UbgdrrhofUH5KZ-uhMD-k@z> (raw)
In-Reply-To: 07d301c469a9$e708f550$0200000a@ALEC
If I recall correctly, the MS compiler uses a subltly different
calling convention/ABI than the "o32" gcc conventions assumed
by MIPS Linux, and certainly the assembler directives will be
different from those assumed by the Linux sources. It *might*
be possible to hack up a MIPS Linux kernel source tree to
build with the MS tool kit, but it would be a lot of work,
some of it subtle.
Regards,
Kevin K.
next prev parent reply other threads:[~2004-07-14 15:03 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 [this message]
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
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='003001c469b4$3b5ae960$10eca8c0@grendel' \
--to=kevink@mips.com \
--cc=a.voropay@vmb-service.ru \
--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