public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "10 dot 50 at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/17885] New: gimplify.c fatal error while expanding a macro
Date: Thu, 07 Oct 2004 19:35:00 -0000 [thread overview]
Message-ID: <20041007193535.17885.10.50@free.fr> (raw)
This snapshot crashes while compiling the kernel of NetBSD in the file kern_lock.c.
Here is the output of the compiler:
----
Reading specs from /usr/pkg/gcc40/lib/gcc/i386-unknown-netbsdelf2.99.9/4.0.0/specs
Configured with: ./configure --x-includes=/usr/pkg/xorg/include
--x-libraries=/usr/pkg/xorg/lib --enable-languages=c c++ objc
--prefix=/usr/pkg/gcc40
Thread model: posix
gcc version 4.0.0 20041003 (experimental)
/usr/pkg/gcc40/libexec/gcc/i386-unknown-netbsdelf2.99.9/4.0.0/cc1 -E -quiet
-nostdinc -v -I. -I../../../../arch -I../../../.. -I../../../../dist/ipf -Di386
-DLKM -DUMASS_DEBUG -DUGEN_DEBUG -DMAXUSERS=32 -D_KERNEL -D_KERNEL_OPT
../../../../kern/kern_lock.c -march=pentium4 -msse2 -mfpmath=sse -Wall -Wno-main
-Wno-format-zero-length -Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes
-Wno-sign-compare -ffreestanding -fno-zero-initialized-in-bss -O2
-fpch-preprocess -o kern_lock.i
#include "..." search starts here:
#include <...> search starts here:
.
../../../../arch
../../../..
../../../../dist/ipf
End of search list.
/usr/pkg/gcc40/libexec/gcc/i386-unknown-netbsdelf2.99.9/4.0.0/cc1
-fpreprocessed kern_lock.i -quiet -dumpbase kern_lock.c -march=pentium4 -msse2
-mfpmath=sse -auxbase kern_lock -O2 -Wall -Wno-main -Wno-format-zero-length
-Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes -Wno-sign-compare
-version -ffreestanding -fno-zero-initialized-in-bss -o kern_lock.s
GNU C version 4.0.0 20041003 (experimental) (i386-unknown-netbsdelf2.99.9)
compiled by GNU C version 4.0.0 20041003 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
../../../../kern/kern_lock.c: In function 'acquire':
../../../../kern/kern_lock.c:233: internal compiler error: in gimplify_expr, at
gimplify.c:3975
The .i files follows.
Have fun folks ;)
Vincent
--
Summary: gimplify.c fatal error while expanding a macro
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: 10 dot 50 at free dot fr
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i386-unknown-netbsdelf2.99.9
GCC target triplet: i386-unknown-netbsdelf2.99.9
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17885
next reply other threads:[~2004-10-07 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 19:35 10 dot 50 at free dot fr [this message]
2004-10-07 19:37 ` [Bug c/17885] " 10 dot 50 at free dot fr
2004-10-07 19:51 ` [Bug middle-end/17885] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-10-07 19:52 ` pinskia at gcc dot gnu dot org
2004-10-16 16:07 ` [Bug middle-end/17885] [4.0 Regression] gimplifing of volatile &a-> reichelt at gcc dot gnu dot org
2004-10-16 16:10 ` pinskia at gcc dot gnu dot org
2004-10-18 14:25 ` pinskia at gcc dot gnu dot org
2004-10-18 22:17 ` pinskia at gcc dot gnu dot org
2004-10-19 17:24 ` cvs-commit at gcc dot gnu dot org
2004-10-20 9:33 ` reichelt at gcc dot gnu dot org
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=20041007193535.17885.10.50@free.fr \
--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).