From: Kenneth Johansson <kenneth.johansson@inn.ericsson.se>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: iweiny@pacbell.net, linuxdev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Linux/PPC BitKeeper tree announcements
Date: Sat, 20 Jan 2001 00:32:10 +0100 [thread overview]
Message-ID: <3A68CE7A.F11219A7@inn.ericsson.se> (raw)
In-Reply-To: 5.0.2.1.2.20010119123352.03511010@mail.munich.netsurf.de
Franz Sirl wrote:
>
> At 02:50 2001-01-19, iweiny@pacbell.net wrote:
>
> >At the risk of sounding stupid I guess I need a newer compiler than egcs for
> >the new kernel trees?
> >
> >fork.c:353: fixed or forbidden register 68 (0) was spilled for class CR0_REGS.
> >This may be due to a compiler bug or to impossible asm
> >statements or clauses.
>
> You shouldn't be using _anything_ older than gcc-2.95.2 on PPC anymore. In
> the meantime the release of gcc-2.95.3 is pending and I would _strongly_
> recommend you to use it.
Why do you so strongly recommend using it?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-19 23:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 23:11 Linux/PPC BitKeeper tree announcements Cort Dougan
2001-01-19 1:50 ` iweiny
2001-01-19 11:40 ` Franz Sirl
2001-01-19 23:32 ` Kenneth Johansson [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=3A68CE7A.F11219A7@inn.ericsson.se \
--to=kenneth.johansson@inn.ericsson.se \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=iweiny@pacbell.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).