public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99880] New: ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 Date: Fri, 02 Apr 2021 02:47:48 +0000 [thread overview] Message-ID: <bug-99880-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99880 Bug ID: 99880 Summary: ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 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: haoxintu at gmail dot com Target Milestone: --- Hi all. This valid program makes GCC crash at -O3. GCC-10 also incurs an ICE with a Segmentation fault, while GCC-10 downwards versions handle this case well. $cat small.c int a, b, c, d, e; void f() { b = 5; for (; b <= 51; b++) ; int g = -8; while (g) { g += 5; int h = 10; do { h -= a = 1; for (; a; a++) ; c *= c >= d >= b; } while (h); c -= e; } } $gcc -w -O3 small.c during GIMPLE pass: vect small.c: In function ‘f’: small.c:2:6: internal compiler error: in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 2 | void f() { | ^ 0x66093f maybe_set_vectorized_backedge_value ../../gcc/tree-vect-loop.c:9161 0xdc466a vect_transform_loop(_loop_vec_info*, gimple*) ../../gcc/tree-vect-loop.c:9650 0xdebbcc try_vectorize_loop_1 ../../gcc/tree-vectorizer.c:1104 0xdec7b1 vectorize_loops() ../../gcc/tree-vectorizer.c:1243 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. $gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/home/tuhaoxin/compilers/gcc/build-20210330/libexec/gcc/x86_64-pc-linux-gnu/11.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../configure --prefix=/home/tuhaoxin/compilers/gcc/build-20210330/ --enable-bootstrap --enable-checking=release --enable-languages=c,c++ -disable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.0.1 20210330 (experimental) (GCC) Reproduced on Godbolt: https://godbolt.org/z/WTje44Wen Thanks, Haoxin
next reply other threads:[~2021-04-02 2:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-02 2:47 haoxintu at gmail dot com [this message] 2021-04-02 11:13 ` [Bug tree-optimization/99880] [10/11 Regression] ICE in maybe_set_vectorized_backedge_value, at tree-vect-loop.c:9161 since r10-3711-g69f8c1aef5cdcc54 marxin at gcc dot gnu.org 2021-04-06 7:42 ` rguenth at gcc dot gnu.org 2021-04-06 11:11 ` rguenth at gcc dot gnu.org 2021-04-06 12:20 ` cvs-commit at gcc dot gnu.org 2021-04-06 12:21 ` [Bug tree-optimization/99880] [10 " rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-26 11:46 ` cvs-commit at gcc dot gnu.org 2021-04-26 11:46 ` rguenth 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-99880-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).