From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>, Mark Haverkamp <markh@osdl.org>
Subject: Re: [PATCH] Re: Weird... 2.6.9 kills FC2 gcc
Date: Mon, 18 Oct 2004 23:15:27 -0500 [thread overview]
Message-ID: <200410182315.27807.dtor_core@ameritech.net> (raw)
In-Reply-To: <41748A9D.2080306@pobox.com>
On Monday 18 October 2004 10:31 pm, Jeff Garzik wrote:
>
> More data points:
>
> No problems at all on x86-64.
>
> No ICE on 32-bit x86 gcc 3.4.2, with 2.6.9 release kernel.
>
> So this ICE appears to be a bug specific to 3.3.x or perhaps Fedora.
>
> Jeff
>
For what it worth this is on mutated RH 8.0:
[dtor@core dtor]$ make
CHK include/linux/version.h
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/asm-i386/asm_offsets.h
CHK include/linux/compile.h
AS arch/i386/kernel/vsyscall.o
include/linux/compiler.h:20: warning: parameter name starts with a digit in #define
include/linux/compiler.h:20: badly punctuated parameter list in #define
make[1]: *** [arch/i386/kernel/vsyscall.o] Error 1
make: *** [arch/i386/kernel] Error 2
[dtor@core dtor]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
--
Dmitry
next prev parent reply other threads:[~2004-10-19 4:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 1:10 Weird... 2.6.9 kills FC2 gcc Jeff Garzik
2004-10-19 1:49 ` Mark Haverkamp
2004-10-19 2:21 ` [PATCH] " Jeff Garzik
2004-10-19 3:31 ` Jeff Garzik
2004-10-19 4:15 ` Dmitry Torokhov [this message]
2004-10-19 6:23 ` Meelis Roos
2004-10-19 14:48 ` Mark Haverkamp
2004-10-19 14:52 ` Jeff Garzik
2004-10-19 6:31 ` Gene Heskett
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=200410182315.27807.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.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.