public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95662] New: [11 regression] ICE at gimple-expr.c:87 since r11-1146 Date: Sat, 13 Jun 2020 03:25:08 +0000 [thread overview] Message-ID: <bug-95662-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95662 Bug ID: 95662 Summary: [11 regression] ICE at gimple-expr.c:87 since r11-1146 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: seurer at linux dot vnet.ibm.com Target Milestone: --- g:1396fa5b91cfa0b3708ec9df33c0bb84386081d6, r11-1146 Note: this may be related to pr95649. I am seeing this on powerpc64 when building two of the spec2006 test cases, 454.calculix and 465.tonto. [spectester@tulibee build_base_ppc64.0000]$ /opt/gcc-spec-nightly/trunk/bin/gfortran -c -o dgesv.o -ISPOOLES -O2 -m64 -mcpu=power8 dgesv.f during GIMPLE pass: cunroll dgesv.f:559:0: 559 | SUBROUTINE DLASWP( N, A, LDA, K1, K2, IPIV, INCX ) | internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in useless_type_conversion_p, at gimple-expr.c:87 0x102172fb tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) /home/spectester/gcc_trunk_git/gcc/gcc/tree.c:9738 0x1074f6f3 tree_class_check /home/spectester/gcc_trunk_git/gcc/gcc/tree.h:3419 0x1074f6f3 useless_type_conversion_p(tree_node*, tree_node*) /home/spectester/gcc_trunk_git/gcc/gcc/gimple-expr.c:87 0x117eed13 chrec_convert_1 /home/spectester/gcc_trunk_git/gcc/gcc/tree-chrec.c:1435 0x117f3bcf chrec_apply(unsigned int, tree_node*, tree_node*) /home/spectester/gcc_trunk_git/gcc/gcc/tree-chrec.c:622 0x10ccdfb3 compute_overall_effect_of_inner_loop(loop*, tree_node*) /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:471 0x10ccb643 analyze_scalar_evolution_1 /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:1960 0x10ccc6db analyze_scalar_evolution(loop*, tree_node*) /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2038 0x10ccd66b instantiate_scev_name /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2335 0x10ccd66b instantiate_scev_r /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2638 0x10ccd2a3 instantiate_scev_binary /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2467 0x10ccd2a3 instantiate_scev_r /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2654 0x10ccd0b7 instantiate_scev_poly /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2412 0x10ccd0b7 instantiate_scev_r /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2643 0x10ccddbb instantiate_scev(edge_def*, loop*, tree_node*) /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.c:2719 0x10d9e783 instantiate_parameters /home/spectester/gcc_trunk_git/gcc/gcc/tree-scalar-evolution.h:63 0x10d9e783 idx_infer_loop_bounds /home/spectester/gcc_trunk_git/gcc/gcc/tree-ssa-loop-niter.c:3612 0x10dafbdb for_each_index(tree_node**, bool (*)(tree_node*, tree_node**, void*), void*) /home/spectester/gcc_trunk_git/gcc/gcc/tree-ssa-loop.c:622 0x10d9ba73 infer_loop_bounds_from_ref /home/spectester/gcc_trunk_git/gcc/gcc/tree-ssa-loop-niter.c:3688 0x10d9ba73 infer_loop_bounds_from_array /home/spectester/gcc_trunk_git/gcc/gcc/tree-ssa-loop-niter.c:3709 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-06-13 3:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-13 3:25 seurer at linux dot vnet.ibm.com [this message] 2020-06-15 6:26 ` [Bug tree-optimization/95662] " rguenth at gcc dot gnu.org 2020-06-15 18:15 ` aldyh at gcc dot gnu.org 2020-06-15 19:01 ` seurer at linux dot vnet.ibm.com 2020-11-28 11:56 ` jakub at gcc dot gnu.org 2020-11-28 14:31 ` seurer 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-95662-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: 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).