From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Re: Weird... 2.6.9 kills FC2 gcc
Date: Mon, 18 Oct 2004 22:21:28 -0400 [thread overview]
Message-ID: <41747A28.2000101@pobox.com> (raw)
In-Reply-To: <1098150587.1384.0.camel@peabody>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Mark Haverkamp wrote:
> On Mon, 2004-10-18 at 18:10, Jeff Garzik wrote:
>
>>The following appears in 2.6.9 release kernel, building with stock FC2
>>gcc on x86, but does not appear in 2.6.9-final:
>>
>>
>>> AS arch/i386/kernel/vsyscall.o
>>>cc1: internal compiler error: Segmentation fault
>>>Please submit a full bug report,
>>>with preprocessed source if appropriate.
>>>See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
>>>make[1]: *** [arch/i386/kernel/vsyscall.o] Error 1
>>>make: *** [arch/i386/kernel] Error 2
>>
>>
>>
>>This is 100% reproducible, at the same location (vsyscall), which is
>>strange because vsyscall didn't change AFAICS.
>>
>>I'll build a gcc 3.4.2 without Fedora Core patches and see if the
>>behavior persists.
>>
>>But in the meantime, if anybody else knows what line of code causes this
>>segfault, please speak up :)
>
>
> As an experiment, I commented out the include of init.h and replaced the
> __INITDATA and __FINIT with the .section and .previous. It then
> compiled OK.
Yep, the same fix (patch attached) works for me.
Jeff
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 455 bytes --]
===== arch/i386/kernel/vsyscall.S 1.1 vs edited =====
--- 1.1/arch/i386/kernel/vsyscall.S 2003-04-22 22:14:57 -04:00
+++ edited/arch/i386/kernel/vsyscall.S 2004-10-18 22:20:32 -04:00
@@ -1,6 +1,5 @@
-#include <linux/init.h>
-__INITDATA
+.section ".init.data","aw"
.globl vsyscall_int80_start, vsyscall_int80_end
vsyscall_int80_start:
@@ -12,4 +11,4 @@
.incbin "arch/i386/kernel/vsyscall-sysenter.so"
vsyscall_sysenter_end:
-__FINIT
+.previous
next prev parent reply other threads:[~2004-10-19 2:21 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 ` Jeff Garzik [this message]
2004-10-19 3:31 ` [PATCH] " Jeff Garzik
2004-10-19 4:15 ` Dmitry Torokhov
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=41747A28.2000101@pobox.com \
--to=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.