public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bunk at stusta dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/35455] New: [4.1/4.2/4.3/4.4 Regression] h8300: internal compiler error: in compute_frame_pointer_to_fb_displacement, at dwarf2out.c:10984
Date: Tue, 04 Mar 2008 07:44:00 -0000 [thread overview]
Message-ID: <bug-35455-9876@http.gcc.gnu.org/bugzilla/> (raw)
$ h8300-linux-gcc -Wp,-MD,fs/.read_write.o.d -nostdinc -isystem
/usr/local/DIR/gcc-h8300-4.3.0-RC-20080301/lib/gcc/h8300-elf/4.3.0/include
-D__KERNEL__ -Iinclude -Iinclude2
-I/home/bunk/linux/kernel-2.6/git/linux-2.6/include -include
include/linux/autoconf.h -I/home/bunk/linux/kernel-2.6/git/linux-2.6/fs -Ifs
-Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -Werror-implicit-function-declaration -Os -fno-stack-protector -mh
-mint32 -fno-builtin -g -D__linux__ -DUTS_SYSNAME=\"uClinux\"
-fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign
-D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(read_write)"
-D"KBUILD_MODNAME=KBUILD_STR(read_write)" -c -o fs/read_write.o
/home/bunk/linux/kernel-2.6/git/linux-2.6/fs/read_write.c
/home/bunk/linux/kernel-2.6/git/linux-2.6/fs/read_write.c: In function
'sys_pwrite64':
/home/bunk/linux/kernel-2.6/git/linux-2.6/fs/read_write.c:427: internal
compiler error: in compute_frame_pointer_to_fb_displacement, at
dwarf2out.c:10984
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: [4.1/4.2/4.3/4.4 Regression] h8300: internal compiler
error: in compute_frame_pointer_to_fb_displacement, at
dwarf2out.c:10984
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bunk at stusta dot de
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: h8300-unknown-elf
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35455
next reply other threads:[~2008-03-04 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 7:44 bunk at stusta dot de [this message]
2008-03-04 7:46 ` [Bug other/35455] " bunk at stusta dot de
2008-03-04 9:36 ` [Bug target/35455] " rguenth at gcc dot gnu dot org
2008-04-15 10:50 ` jakub at gcc dot gnu dot org
2008-05-19 20:34 ` jsm28 at gcc dot gnu dot org
2008-07-04 23:03 ` [Bug target/35455] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-03-31 20:47 ` [Bug target/35455] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:39 ` rguenth at gcc dot gnu dot org
2010-02-24 20:22 ` law at redhat dot com
2010-05-22 18:25 ` [Bug target/35455] [4.3/4.4/4.5/4.6 " rguenth 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=bug-35455-9876@http.gcc.gnu.org/bugzilla/ \
--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).