Bug 37637 - gcc has problems compiling the kernel 2.4.3 with --march=k6
Summary: gcc has problems compiling the kernel 2.4.3 with --march=k6
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gcc
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
: 37636 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-04-25 16:45 UTC by Suchandra Thapa
Modified: 2007-04-18 16:32 UTC (History)
0 users

Clone Of:
Last Closed: 2001-04-25 17:28:13 UTC

Attachments (Terms of Use)
kernel config file (15.82 KB, text/plain)
2001-04-25 16:46 UTC, Suchandra Thapa
no flags Details

Description Suchandra Thapa 2001-04-25 16:45:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.3 i586)

Giving the processor type as k6 compiles the kernel with a -march=k6 flag
which seems to cause the problem.  Switching processor type to pentium tsc
allows the kernel to compile cleanly..  This problem didn't show up when I
was using gcc-2.96-69 but is present in gcc-2.96-81.

Reproducible: Always
Steps to Reproduce:
1. make menuconfig and choose k6 as processor
2. try to compile kernel

Actual Results:  gcc -D__KERNEL__ -I/usr/src/linux-2.4.3/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=k6    -c -o setup.o setup.c
setup.c: In function `check_cx686_slop':
setup.c:1143: Internal error: Segmentation fault.
Please submit a full bug report.

Comment 1 Suchandra Thapa 2001-04-25 16:46:54 UTC
Created attachment 16409 [details]
kernel config file

Comment 2 Bill Nottingham 2001-04-25 17:03:21 UTC
*** Bug 37636 has been marked as a duplicate of this bug. ***

Comment 3 Jakub Jelinek 2001-04-25 17:15:33 UTC
Is it reproduceable? If yes, can you run
gcc -D__KERNEL__ -I/usr/src/linux-2.4.3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -mpreferred-stack-boundary=2 -march=k6    -c -o setup.o setup.c -save-temps -v
and attach here setup.i it creates?

Comment 4 Suchandra Thapa 2001-04-25 17:28:09 UTC
No, apparently my memory or cpu is flaky because I'm getting seg faults in
random places during compilation.  Sorry about the spurious bug report.

Note You need to log in before you can comment on or make changes to this bug.