From: Adrian Bunk <bunk@fs.tum.de>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.49-ac2
Date: Thu, 28 Nov 2002 02:40:38 +0100 [thread overview]
Message-ID: <20021128014038.GV21307@fs.tum.de> (raw)
In-Reply-To: <200211262321.gAQNLPR12191@devserv.devel.redhat.com>
Hi Alan,
I'm getting the following compile error in 2.5.49-ac{1,2} but not in
2.5.49 (I haven't tried older -ac kernels):
<-- snip -->
...
gcc -Wp,-MD,arch/i386/math-emu/.reg_ld_str.o.d -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=k6 -p -Iarch/i386/mach-generic
-Iarch/i386/mach-defaults -DPARANOID -fno-builtin -nostdinc -iwithprefix include
-DKBUILD_BASENAME=reg_ld_str -DKBUILD_MODNAME=reg_ld_str -c -o
arch/i386/math-emu/reg_ld_str.o arch/i386/math-emu/reg_ld_str.c
cpp0: output pipe has been closed
gcc: Internal compiler error: program cc1 got fatal signal 11
make[1]: *** [arch/i386/math-emu/reg_ld_str.o] Error 1
make: *** [arch/i386/math-emu] Error 2
{standard input}: Assembler messages:
{standard input}:2235: Warning: end of file not at end of a line; newline inserted
{standard input}:2438: Error: suffix or operands invalid for `mov'
<-- snip -->
This is with a 2.95 gcc (the one in Debian unstable). Compiling with
3.2.1 or setting the optimization to -O1 fixes the problem so it might
be an optimizer bug.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2002-11-28 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 23:21 Alan Cox
2002-11-27 5:03 ` Murray J. Root
2002-11-28 1:40 ` Adrian Bunk [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=20021128014038.GV21307@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®