From: Keith M Wesolowski <wesolows@foobazco.org>
To: nick@snowman.net
Cc: Justin Carlson <carlson@sibyte.com>, linux-mips@oss.sgi.com
Subject: Re: Embedded MIPS/Linux Needs
Date: Thu, 22 Mar 2001 11:22:29 -0800 [thread overview]
Message-ID: <20010322112229.A5617@foobazco.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0103221402430.19179-100000@ns>; from nick@snowman.net on Thu, Mar 22, 2001 at 02:03:43PM -0500
On Thu, Mar 22, 2001 at 02:03:43PM -0500, nick@snowman.net wrote:
> (It sorta produces useable code... usually..... on tuesdays... if it's a
> blue moon)
gcc 3.0 for mips64 requires hacks to even accept the arguments the
kernel compile wants to give, and even then it reliably produces
extremely incorrect code. For example:
int i = 0;
prom_printf ("%d", i);
Might yield something like
-14777223
- basically, anything but 0. The code that causes this is horribly
wrong that it wasn't even worth looking at. There are all sorts of
similar, related, and dissimilar problems.
On the other hand, the same compiler for mips (not 64) reliably
produces working 2.4 kernels...
--
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
"I should have crushed his marketing-addled skull with a fucking bat."
next prev parent reply other threads:[~2001-03-22 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 19:02 Embedded MIPS/Linux Needs Justin Carlson
2001-03-22 19:03 ` nick
2001-03-22 19:22 ` Keith M Wesolowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 12:27 Phil Thompson
2001-03-22 11:48 Kevin D. Kissell
2001-03-22 11:48 ` Kevin D. Kissell
2001-03-22 14:01 ` Jay Carlson
2001-03-22 14:01 ` Jay Carlson
2001-03-22 18:32 ` Jun Sun
2001-03-22 14:17 ` Mike McDonald
2001-03-22 18:23 ` Jeff Harrell
2001-03-22 18:23 ` Jeff Harrell
2001-03-26 3:01 ` Joe deBlaquiere
2001-03-26 3:23 ` Keith Owens
2001-03-26 4:06 ` Keith M Wesolowski
2001-03-26 17:25 ` Florian Lohoff
2001-03-26 18:47 ` Joe deBlaquiere
2001-03-26 23:24 ` Jun Sun
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=20010322112229.A5617@foobazco.org \
--to=wesolows@foobazco.org \
--cc=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.com \
--cc=nick@snowman.net \
/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