public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46304] [4.5 Regression] g++ crashes with ICE in bitmap_first_set_bit, at bitmap.c:770 Date: Fri, 05 Nov 2010 11:20:00 -0000 [thread overview] Message-ID: <bug-46304-4-Zokv0DYbfA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46304-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46304 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW AssignedTo|rguenth at gcc dot gnu.org |unassigned at gcc dot | |gnu.org --- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-05 11:20:00 UTC --- Hm. In 4.6 two different COMPLEX_EXPRs are built by tsubst, via cp_build_binary_op (PLUS_EXPR, ...). In 4.5 we end up with a COMPLEX_EXPR at tsubst time which we don't handle explicitly but pass through from tsubst_copy default case (which would ICE on trunk). Jason?
next prev parent reply other threads:[~2010-11-05 11:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-04 17:14 [Bug c++/46304] New: " apataki at apataki dot net 2010-11-04 21:01 ` [Bug c++/46304] " apataki at apataki dot net 2010-11-04 23:05 ` hjl.tools at gmail dot com 2010-11-05 5:57 ` jason at gcc dot gnu.org 2010-11-05 10:49 ` [Bug c++/46304] [4.5 Regression] " rguenth at gcc dot gnu.org 2010-11-05 10:55 ` rguenth at gcc dot gnu.org 2010-11-05 11:20 ` rguenth at gcc dot gnu.org [this message] 2010-11-12 15:16 ` rguenth at gcc dot gnu.org 2010-11-14 11:51 ` rguenth at gcc dot gnu.org 2010-11-16 15:13 ` apataki at apataki dot net 2010-12-16 13:10 ` rguenth at gcc dot gnu.org 2011-04-18 14:34 ` rguenth at gcc dot gnu.org 2011-04-20 0:44 ` jason at gcc dot gnu.org 2011-04-20 6:31 ` jason at gcc dot gnu.org 2011-04-20 6:32 ` jason at gcc dot gnu.org 2011-04-20 6:34 ` jason at gcc dot gnu.org 2011-04-20 6:50 ` jason at gcc dot gnu.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-46304-4-Zokv0DYbfA@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: 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).