public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21687] New: [4.0/4.1 Regression] ICE on valid code
Date: Fri, 20 May 2005 22:01:00 -0000	[thread overview]
Message-ID: <20050520220116.21687.pinskia@gcc.gnu.org> (raw)

I know this goes against all the rules for filing bugs but when I supply -save-temps, I don't get an ICE.
The code is the code from PR 21685 with one exception, the following 2 lines are commented out (this 
makes this code valid):
              const value_iterator end = union_f(sets.begin(), sets.end(), 
output.begin()); 

It fails with "4.0.0 20050113"
The ICE is:
t.cc: In member function 'void OKlib::SetAlgorithms::Test_Union<Union>::perform_test_trivial()':
t.cc:94: internal compiler error: tree check: expected statement_list, have type_expr in 
finish_compound_stmt, at cp/semantics.c:1113
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

-- 
           Summary: [4.0/4.1 Regression] ICE on valid code
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: critical
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc-apple-darwin7.8.0
  GCC host triplet: powerpc-apple-darwin7.8.0
GCC target triplet: powerpc-apple-darwin7.8.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21687


             reply	other threads:[~2005-05-20 22:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 22:01 pinskia at gcc dot gnu dot org [this message]
2005-07-01  4:32 ` [Bug c++/21687] " pinskia at gcc dot gnu dot org
2005-07-01 19:10 ` pinskia at gcc dot gnu dot org
2005-07-06 14:37 ` pinskia at gcc dot gnu dot org
2005-07-17 22:45 ` mmitchel at gcc dot gnu dot org
2005-07-22 21:03 ` steven at gcc dot gnu dot org
2005-07-22 21:10 ` pinskia at gcc dot gnu dot org
2005-07-22 23:08 ` pinskia at gcc dot gnu dot org
2005-07-22 23:09 ` [Bug c++/21687] [4.0/4.1 Regression] ICE in GC with local class inside a template function pinskia at gcc dot gnu dot org
2005-07-22 23:22 ` pinskia at gcc dot gnu dot org
2005-07-23  0:43 ` pinskia at gcc dot gnu dot org
2005-07-23 15:54 ` janis at gcc dot gnu dot org
2005-07-23 16:26 ` pinskia at gcc dot gnu dot org
2005-07-25 18:52 ` rth at gcc dot gnu dot org
2005-08-25 16:46 ` pinskia at gcc dot gnu dot org
2005-08-31 22:10 ` mmitchel at gcc dot gnu dot org
2005-09-02 18:23 ` cvs-commit at gcc dot gnu dot org
2005-09-02 18:31 ` cvs-commit at gcc dot gnu dot org
2005-09-02 18:31 ` mmitchel at gcc dot gnu dot org
2005-09-03 18:19 ` cvs-commit at gcc dot gnu dot org
2005-09-03 18:30 ` cvs-commit 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=20050520220116.21687.pinskia@gcc.gnu.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).