public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: k_fukui@highway.ne.jp To: gcc-gnats@gcc.gnu.org Subject: bootstrap/7027: Internal compiler error in dwarf2out_frame_debug_expr, at dwarf2out.c:1517 Date: Fri, 14 Jun 2002 03:46:00 -0000 [thread overview] Message-ID: <20020614084432.591.qmail@sources.redhat.com> (raw) >Number: 7027 >Category: bootstrap >Synopsis: Internal compiler error in dwarf2out_frame_debug_expr, at dwarf2out.c:1517 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jun 14 01:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: k_fukui@highway.ne.jp >Release: gcc-3.2 20020613 (experimental) >Organization: >Environment: powerpc-unknown-linux-gnu >Description: ./xgcc -B ./ -O2 -c -DIN_GCC -g -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../include \ -DSTANDARD_STARTFILE_PREFIX=\"../../../\" -DSTANDARD_EXEC_PREFIX=\"/usr/lib/gc c-lib/\" -DDEFAULT_TARGET_VERSION=\"3.2\" -DDEFAULT_TARGET_MACHINE=\"powerpc-unk nown-linux-gnu\" -DSTANDARD_BINDIR_PREFIX=\"/usr/bin/\" -DTOOLDIR_BASE_PREFIX=\" ../../../../\" `test "X${SHLIB_LINK}" = "X" || test "yes" != "yes" || echo "-DEN ABLE_SHARED_LIBGCC"` `test "X${SHLIB_MULTILIB}" = "X" || echo "-DNO_SHARED_LIBGC C_MULTILIB"` \ ../../gcc/protoize.c -o protoize.o) ../../gcc/protoize.c: In function `safe_write': ../../gcc/protoize.c:645: internal compiler error: Internal compiler error in dw arf2out_frame_debug_expr, at dwarf2out.c:1517 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. make: *** [protoize.o] Error 1 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-06-14 8:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020614084432.591.qmail@sources.redhat.com \ --to=k_fukui@highway.ne.jp \ --cc=gcc-gnats@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: linkBe 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).