public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61688] New: [4.10 Regression] ICE: tree check: expected record_type or union_type or qual_union_type, have array_type in ipa_binfo_from_known_type_jfunc
Date: Thu, 03 Jul 2014 14:56:00 -0000	[thread overview]
Message-ID: <bug-61688-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61688

            Bug ID: 61688
           Summary: [4.10 Regression] ICE: tree check: expected
                    record_type or union_type or qual_union_type, have
                    array_type in ipa_binfo_from_known_type_jfunc
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rmansfield at qnx dot com

Created attachment 33062
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33062&action=edit
preprocessed src

$ ./xgcc -B. ~/ice.ii -c -O2
/home/ryan/ice.ii:30:27: warning: inline function 'UBool
icu::UnicodeString::isEmpty() const' used but never defined
        inline UBool       isEmpty (void) const;
                           ^
/home/ryan/ice.ii: In member function 'void
icu::DateIntervalFormat::concatSingleDate2TimeInterval(const UChar*,
std::int32_t, const icu::UnicodeString&, UCalendarDateFields, UErrorCode&)':
/home/ryan/ice.ii:58:15: internal compiler error: tree check: expected
record_type or union_type or qual_union_type, have array_type in
ipa_binfo_from_known_type_jfunc, at ipa-prop.c:555
      void     DateIntervalFormat::concatSingleDate2TimeInterval (const UChar *
format,              int32_t formatLen,              const UnicodeString &     
        datePattern,              UCalendarDateFields              field,      
       UErrorCode & status)     {
               ^
0xd98154 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
    ../../gcc/tree.c:9220
0x9e1327 tree_check3
    ../../gcc/tree.h:2771
0x9e1327 ipa_binfo_from_known_type_jfunc(ipa_jump_func*)
    ../../gcc/ipa-prop.c:555
0x9e1eba ipa_intraprocedural_devirtualization(gimple_statement_base*)
    ../../gcc/ipa-prop.c:2467
0xcb7f8f eliminate_dom_walker::before_dom_children(basic_block_def*)
    ../../gcc/tree-ssa-pre.c:4365
0xfca602 dom_walker::walk(basic_block_def*)
    ../../gcc/domwalk.c:177
0xcb6412 eliminate
    ../../gcc/tree-ssa-pre.c:4493
0xcb6693 execute
    ../../gcc/tree-ssa-pre.c:4910
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.

gcc version 4.10.0 20140702 (experimental) [trunk revision 212230] (GCC)


             reply	other threads:[~2014-07-03 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 14:56 rmansfield at qnx dot com [this message]
2014-07-03 15:12 ` [Bug ipa/61688] " trippels at gcc dot gnu.org
2014-07-03 16:59 ` rmansfield at qnx dot com
2014-07-03 17:26 ` trippels at gcc dot gnu.org
2014-07-03 21:38 ` jakub at gcc dot gnu.org
2014-07-07 12:00 ` burnus at gcc dot gnu.org
2014-09-25 20:19 ` [Bug ipa/61688] [5 " hubicka 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-61688-4@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: 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).