public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jens.troeger@light-speed.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/10023: g++ Internal Compiler Error at -O2-4
Date: Tue, 11 Mar 2003 07:36:00 -0000 [thread overview]
Message-ID: <20030311073337.10375.qmail@sources.redhat.com> (raw)
>Number: 10023
>Category: c++
>Synopsis: g++ Internal Compiler Error at -O2-4
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Mar 11 07:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: jens.troeger@light-speed.de
>Release: g++ 2.95
>Organization:
>Environment:
YellowDog Linux 2.3 on PPC (PowerBook)
>Description:
hey... what can i say? here it comes:
savage@tigger:~/savage/uqbt> g++ -v -save-temps -O2 -g3 -o hello-trace hello-trace.cc
Reading specs from /usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/specs
gcc version 2.95.4 20010319 (prerelease/franzo/20011204)
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/cpp0 -lang-c++ -v -D__GNUC__=2 -D__GNUG__=2 -D__GNUC_MINOR__=95 -D__cplusplus -DPPC -D__ELF__ -Dpowerpc -D__PPC__ -D__ELF__ -D__powerpc__ -D__PPC -D__powerpc -Acpu(powerpc) -Amachine(powerpc) -D__EXCEPTIONS -D__CHAR_UNSIGNED__ -D__OPTIMIZE__ -g3 -D_CALL_SYSV -D_BIG_ENDIAN -D__BIG_ENDIAN__ -Amachine(bigendian) -D_ARCH_PPC -D__unix__ -D__linux__ -Dunix -D__unix -Dlinux -D__linux -Asystem(unix) -Asystem(posix) hello-trace.cc hello-trace.ii
GNU CPP version 2.95.4 20010319 (prerelease/franzo/20011204) (PowerPC GNU/Linux)
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/../../../../include/g++-3
/usr/local/include
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/include
/usr/include
End of search list.
The following default directories have been omitted from the search path:
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/../../../../ppc-yellowdog-linux/include
End of omitted list.
/usr/lib/gcc-lib/ppc-yellowdog-linux/2.95.4/cc1plus hello-trace.ii -quiet -dumpbase hello-trace.cc -g3 -O2 -version -o hello-trace.s
GNU C++ version 2.95.4 20010319 (prerelease/franzo/20011204) (ppc-yellowdog-linux) compiled by GNU C version 2.95.4 20010319 (prerelease/franzo/20011204).
hello-trace.cc: In function `void execute(int)':
hello-trace.cc:1637: Internal compiler error:
hello-trace.cc:1637: Internal compiler error in `mark_jump_label', at jump.c:3725
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
i can send you the source files?
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-03-11 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 7:36 jens.troeger [this message]
2003-03-11 11:16 Steven Bosscher
2003-03-11 15:01 bangerth
2003-03-11 22:56 Jens Troeger
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=20030311073337.10375.qmail@sources.redhat.com \
--to=jens.troeger@light-speed.de \
--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: 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).