public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harold at alum dot mit dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/23948] internal compiler error: verify_stmts failed
Date: Sun, 18 Sep 2005 18:02:00 -0000 [thread overview]
Message-ID: <20050918180243.5612.qmail@sourceware.org> (raw)
In-Reply-To: <20050918131230.23948.harold@alum.mit.edu>
------- Additional Comments From harold at alum dot mit dot edu 2005-09-18 18:02 -------
OK, please bear with me. I'm not as talented as you at this, but I'm trying.
I think we're both using the 9/16/05 build, since the top entry in the
"ChangeLog" file is 9/16/05.
The compile command that generates the error is:
g++-4.1 -DHAVE_CONFIG_H -I. -I. -I.. -I ./win -I../lib -I../api -I../db
-I../RSAEuro/source -I../client -I../tools -I../sched -pthread -include
../config.h -O3 -D__NO_CTYPE -I../lib -I../api -I../db -I../RSAEuro/source
-I../client -I../tools -I../sched -pthread -include ../config.h -DACML -O3
-ffast-math -funroll-all-loops -fpeel-loops -ftracer -funswitch-loops
-ftree-vectorize -march=k8 -g -pthread -MT boinc_client-cs_scheduler.o -MD -MP
-MF ".deps/boinc_client-cs_scheduler.Tpo" -c -o boinc_client-cs_scheduler.o
cs_scheduler.C cs_scheduler.C: In member function 'int
CLIENT_STATE::make_scheduler_request(PROJECT*)':
cs_scheduler.C:200: error: statement marked for throw in middle of block
# bufD.54331_943(ab) = V_MAY_DEF <bufD.54331_939>;
# SFT.1187D.68458_944(ab) = V_MAY_DEF <SFT.1187D.68458_940>;
# SFT.1188D.68459_945(ab) = V_MAY_DEF <SFT.1188D.68459_941>;
# SFT.1189D.68460_946(ab) = V_MAY_DEF <SFT.1189D.68460_942>;
prrsD.54346_136 = potentially_runnable_resource_share (thisD.54329_135);
cs_scheduler.C:200: internal compiler error: verify_stmts failed
Please submit a full bug report,
with preprocessed source if appropriate.
>From this command, do you need me to post any other files? I can't really tell,
to be honest, since I'm not too sure what all those -M flags do.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23948
next prev parent reply other threads:[~2005-09-18 18:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 13:12 [Bug c++/23948] New: " harold at alum dot mit dot edu
2005-09-18 13:16 ` [Bug c++/23948] " harold at alum dot mit dot edu
2005-09-18 15:30 ` harold at alum dot mit dot edu
2005-09-18 16:33 ` pinskia at gcc dot gnu dot org
2005-09-18 18:02 ` harold at alum dot mit dot edu [this message]
2005-09-18 18:06 ` pinskia at gcc dot gnu dot org
2005-09-18 18:10 ` pinskia at gcc dot gnu dot org
2005-09-18 18:17 ` [Bug tree-optimization/23948] [4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-18 18:54 ` pinskia at gcc dot gnu dot org
2005-09-20 21:28 ` janis187 at us dot ibm dot com
2005-09-21 8:13 ` bonzini at gcc dot gnu dot org
2005-09-21 14:19 ` rguenth at gcc dot gnu dot org
2005-09-21 14:33 ` paolo dot bonzini at lu dot unisi dot ch
2005-09-21 14:44 ` rguenth at gcc dot gnu dot org
2005-09-22 7:00 ` bonzini at gcc dot gnu dot org
2005-09-22 7:09 ` bonzini at gcc dot gnu dot org
2005-09-23 9:58 ` bonzini at gcc dot gnu dot org
2005-09-25 12:48 ` bonzini 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=20050918180243.5612.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).