From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: a.voropay@vmb-service.ru, linux-mips@linux-mips.org
Subject: Re: MS VC++ compiler / MIPS
Date: Thu, 15 Jul 2004 02:39:14 +0200 [thread overview]
Message-ID: <20040715003914.GB25279@linux-mips.org> (raw)
In-Reply-To: <003001c469b4$3b5ae960$10eca8c0@grendel>
On Wed, Jul 14, 2004 at 05:07:06PM +0200, Kevin D. Kissell wrote:
> 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.
A few years ago we got SGI's IA-64 kernel to compile with their Pro64
compiler. Despite the usually rather dramatic superiority of Pro64's
code generation compared to the gcc of that time - half the time to
generate twice as fast application code was common - the huge effort
it took was essentially wasted time to achieve a hard to meassure amount
of extra performance. Most of the kernel code is well optimized, was
written with being compiled by gcc in mind and performance is more
limited by the hardware and kernel algorithms than by the compiler's
code generation. So I wouldn't invest any time into trying to get the
kernel working on yet another non-gcc compiler ...
Ralf
prev parent reply other threads:[~2004-07-15 0:39 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
2004-07-15 0:39 ` Ralf Baechle [this message]
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=20040715003914.GB25279@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.