public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/17635] [4.0 regression] ICE in verify_ssa: type mismatch Date: Thu, 23 Sep 2004 15:36:00 -0000 [thread overview] Message-ID: <20040923153618.10745.qmail@sourceware.org> (raw) In-Reply-To: <20040923141106.17635.bangerth@dealii.org> ------- Additional Comments From bangerth at dealii dot org 2004-09-23 15:36 ------- Here's the smallest I can get it within the constraints of my time: ---------------------------- #include <vector> template<typename T> T max_element(T __first, T __last) { if (__first == __last) return __first; T __result = __first; while (++__first != __last) if (*__result < *__first) __result = __first; return __result; } struct S { std::vector<bool> used; }; struct A { unsigned int foo (); std::vector<S*> s; }; struct Accessor { A *a; bool used () { return this->a->s[0]->used[0]; } void bar () { this->a->s[0]->used.size(); } }; struct D { bool baz (); Accessor accessor; void bar () { accessor.bar(); if (this->accessor.used()) return; } }; unsigned int A::foo () { std::vector<int> v; for (D d; d.baz(); d.bar()) +v[0]; return (*max_element (v.begin(), v.end())); } ------------------------------- g/x> /home/bangerth/bin/gcc-4.0-pre/bin/c++ -O3 -ftree-vectorize -c x.cc x.cc: In member function `unsigned int A::foo()': x.cc:47: error: Type mismatch between an SSA_NAME and its symbol. x.cc:47: error: Missing definition for SSA_NAME: D.14109_789in statement: D.14109_788 = PHI <D.14109_149(29), D.14109_789(6)>; x.cc:47: internal compiler error: verify_ssa failed. Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17635
next prev parent reply other threads:[~2004-09-23 15:36 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-23 14:11 [Bug tree-optimization/17635] New: " bangerth at dealii dot org 2004-09-23 14:12 ` [Bug tree-optimization/17635] " bangerth at dealii dot org 2004-09-23 14:14 ` pinskia at gcc dot gnu dot org 2004-09-23 14:17 ` steven at gcc dot gnu dot org 2004-09-23 14:20 ` bangerth at ices dot utexas dot edu 2004-09-23 14:26 ` steven at gcc dot gnu dot org 2004-09-23 14:29 ` bangerth at ices dot utexas dot edu 2004-09-23 14:46 ` pinskia at gcc dot gnu dot org 2004-09-23 15:36 ` bangerth at dealii dot org [this message] 2004-09-23 17:08 ` pinskia at gcc dot gnu dot org 2004-09-23 22:06 ` dpatel at apple dot com 2004-09-23 22:29 ` pinskia at gcc dot gnu dot org 2004-09-24 0:08 ` reichelt at gcc dot gnu dot org 2004-09-24 0:11 ` reichelt at gcc dot gnu dot org 2004-09-24 0:18 ` pinskia at gcc dot gnu dot org 2004-09-24 0:51 ` dpatel at apple dot com 2004-09-24 17:30 ` pinskia at gcc dot gnu dot org 2004-10-01 18:08 ` pinskia at gcc dot gnu dot org 2004-10-01 18:09 ` pinskia at gcc dot gnu dot org 2004-10-01 18:10 ` pinskia at gcc dot gnu dot org 2004-10-06 1:14 ` dpatel at apple dot com 2004-10-14 18:40 ` pinskia at gcc dot gnu dot org 2004-11-13 13:23 ` reichelt at gcc dot gnu dot org 2004-11-13 13:55 ` reichelt at gcc dot gnu dot org 2004-11-17 22:13 ` dpatel at apple dot com 2004-11-18 12:46 ` reichelt 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=20040923153618.10745.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: 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).