public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/97769] New: [11 Regression] vectorizer ICE when building perlbench in SPECCPU 2017 Date: Mon, 09 Nov 2020 18:25:57 +0000 [thread overview] Message-ID: <bug-97769-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97769 Bug ID: 97769 Summary: [11 Regression] vectorizer ICE when building perlbench in SPECCPU 2017 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: tnfchris at gcc dot gnu.org Target Milestone: --- Created attachment 49528 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49528&action=edit reproducer for ice With vectorizer enabled the perlbench benchmark ICEs if you bump up the inliner limit: during GIMPLE pass: vect tmp.i: In function 'fn3': tmp.i:25:1: internal compiler error: in vect_update_misalignment_for_peel, at tree-vect-data-refs.c:1196 25 | fn3() { fn2(&(&c)->otmp); } | ^~~ 0x19f9b43 vect_update_misalignment_for_peel ../../gcc-fsf/gcc/tree-vect-data-refs.c:1193 0x19f9def vect_get_peeling_costs_all_drs ../../gcc-fsf/gcc/tree-vect-data-refs.c:1481 0x19fb83b vect_peeling_hash_get_lowest_cost(_vect_peel_info**, _vect_peel_extended_info*) ../../gcc-fsf/gcc/tree-vect-data-refs.c:1508 0x1a068cb void hash_table<peel_info_hasher, false, xcallocator>::traverse_noresize<_vect_peel_extended_info*, &(vect_peeling_hash_get_lowest_cost(_vect_peel_info**, _vect_peel_extended_info*))>(_vect_peel_extended_info*) ../../gcc-fsf/gcc/hash-table.h:1081 0x1a068cb void hash_table<peel_info_hasher, false, xcallocator>::traverse<_vect_peel_extended_info*, &(vect_peeling_hash_get_lowest_cost(_vect_peel_info**, _vect_peel_extended_info*))>(_vect_peel_extended_info*) ../../gcc-fsf/gcc/hash-table.h:1102 0x1a068cb vect_peeling_hash_choose_best_peeling ../../gcc-fsf/gcc/tree-vect-data-refs.c:1557 0x1a068cb vect_enhance_data_refs_alignment(_loop_vec_info*) ../../gcc-fsf/gcc/tree-vect-data-refs.c:2058 0x10ef27f vect_analyze_loop_2 ../../gcc-fsf/gcc/tree-vect-loop.c:2351 0x10f03b3 vect_analyze_loop(loop*, vec_info_tmpred*) ../../gcc-fsf/gcc/tree-vect-loop.c:2895 0x1118d83 try_vectorize_loop_1 ../../gcc-fsf/gcc/tree-vectorizer.c:995 0x11194ff vectorize_loops() ../../gcc-fsf/gcc/tree-vectorizer.c:1230 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. The attached testcase reproduces this at -O3 with no other options.
next reply other threads:[~2020-11-09 18:25 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-09 18:25 tnfchris at gcc dot gnu.org [this message] 2020-11-09 18:27 ` [Bug c/97769] " tnfchris at gcc dot gnu.org 2020-11-10 8:06 ` [Bug middle-end/97769] " rguenth at gcc dot gnu.org 2020-11-10 12:33 ` rguenth at gcc dot gnu.org 2020-11-10 12:41 ` cvs-commit at gcc dot gnu.org 2020-11-10 12:41 ` rguenth at gcc dot gnu.org 2020-11-10 12:43 ` tnfchris 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-97769-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).