public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "axel at freakout dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32264] gcc 4.2.0 compiled vanilla kernel 2.4.34.5 crashes when VIA C3 optimized -march=c3
Date: Thu, 02 Aug 2007 15:06:00 -0000 [thread overview]
Message-ID: <20070802150602.27033.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32264-14676@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from axel at freakout dot de 2007-08-02 15:05 -------
Subject: Re: gcc 4.2.0 compiled vanilla kernel
2.4.34.5 crashes when VIA C3 optimized -march=c3
According to pluto at agmk dot net:
>
> my gcc-4.2.1 (which is almost like FSF release) produces for attached
> preprocessed file reasonable code that contains interrupt routines.
>
the compiler is build form the gnu distribution on this machine and
has compiled lots of packages without a problem. also 2.4.35 kernels
for i386(plain) and P3-optimized work without any problem within the
same build environment and this compiler. what should i verify with
my gcc-4.2.1 installation?
maybe the options for the Linux build system make the difference?:
+ gcc4 --version
gcc4 (GCC) 4.2.1
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+ gcc4 -D__KERNEL__ --save-temps -I/src/kernel/linux-2.4.35-ARX/include \
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing \
-fno-common -fno-builtin-sprintf -fomit-frame-pointer -Wno-pointer-sign \
-pipe -mpreferred-stack-boundary=2 -march=c3 -falign-functions=0
-falign-jumps=0 \
-falign-loops=0 -fno-unit-at-a-time -nostdinc -iwithprefix include \
-DKBUILD_BASENAME=i8259 -c -o i8259.o i8259.c
gcc4: warning: -pipe ignored because -save-temps specified
+ nm i8259.o | grep inter
00000030 b IRQ0x00_interrupt
00000040 b IRQ0x01_interrupt
00000050 b IRQ0x02_interrupt
00000060 b IRQ0x03_interrupt
00000070 b IRQ0x04_interrupt
00000080 b IRQ0x05_interrupt
00000090 b IRQ0x06_interrupt
000000a0 b IRQ0x07_interrupt
000000b0 b IRQ0x08_interrupt
000000c0 b IRQ0x09_interrupt
000000d0 b IRQ0x0a_interrupt
000000e0 b IRQ0x0b_interrupt
000000f0 b IRQ0x0c_interrupt
00000100 b IRQ0x0d_interrupt
00000110 b IRQ0x0e_interrupt
00000120 b IRQ0x0f_interrupt
00000010 b common_interrupt
00000000 D interrupt
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32264
next prev parent reply other threads:[~2007-08-02 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 20:17 [Bug target/32264] New: " gcc-bugzilla at gcc dot gnu dot org
2007-06-08 20:20 ` [Bug target/32264] " pinskia at gcc dot gnu dot org
2007-06-08 20:25 ` axel at freakout dot de
2007-06-09 10:27 ` rguenth at gcc dot gnu dot org
2007-06-10 10:05 ` axel at freakout dot de
2007-06-10 13:00 ` axel at freakout dot de
2007-07-31 18:55 ` axel at freakout dot de
2007-08-01 17:37 ` pluto at agmk dot net
2007-08-01 19:25 ` axel at freakout dot de
2007-08-02 13:29 ` pluto at agmk dot net
2007-08-02 15:06 ` axel at freakout dot de [this message]
2007-08-02 19:42 ` pluto at agmk dot net
2007-08-02 19:55 ` axel at freakout dot de
2007-08-03 19:55 ` pluto at agmk dot net
2007-08-04 10:45 ` axel at freakout dot de
2007-08-05 8:02 ` pluto at agmk dot net
2007-08-05 15:40 ` w at 1wt dot eu
2007-08-05 16:05 ` schwab at suse dot de
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=20070802150602.27033.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).