public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110461] [14 regression] ICE when building openh264 with new vector_type checking Date: Wed, 28 Jun 2023 22:20:19 +0000 [thread overview] Message-ID: <bug-110461-4-z9f41yOhOM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110461-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110461 seurer at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seurer at gcc dot gnu.org --- Comment #9 from seurer at gcc dot gnu.org --- I am seeing probably the same error with one gcc test case and it started with g:fe48f2651334bc4d96b6df6b2bb6b29fcb732a83, r14-2150-gfe48f2651334bc as that wasn't mentioned here that I saw. make -k check-gcc RUNTESTFLAGS="compile.exp=gcc.c-torture/compile/pr46883.c" FAIL: gcc.c-torture/compile/pr46883.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (internal compiler error: tree check: expected none of vector_type, have vector_type in vect_recog_rotate_pattern, at tree-vect-patterns.cc:3634) FAIL: gcc.c-torture/compile/pr46883.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors) FAIL: gcc.c-torture/compile/pr46883.c -O3 -g (internal compiler error: tree check: expected none of vector_type, have vector_type in vect_recog_rotate_pattern, at tree-vect-patterns.cc:3634) FAIL: gcc.c-torture/compile/pr46883.c -O3 -g (test for excess errors) # of expected passes 6 # of unexpected failures 4 spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc -B/home/seurer/gcc/git/build/gcc-test/gcc/ -fdiagnostics-plain-output -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions -w -c -o pr46883.o /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.c-torture/compile/pr46883.c during GIMPLE pass: slp /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.c-torture/compile/pr46883.c: In function 'bar': /home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.c-torture/compile/pr46883.c:1:6: internal compiler error: tree check: expected none of vector_type, have vector_type in vect_recog_rotate_pattern, at tree-vect-patterns.cc:3634 0x10291b5f tree_not_check_failed(tree_node const*, char const*, int, char const*, ...) /home/seurer/gcc/git/gcc-test/gcc/tree.cc:8936 0x11b9f833 tree_not_check(tree_node*, char const*, int, char const*, tree_code) /home/seurer/gcc/git/gcc-test/gcc/tree.h:3581 0x11b9f833 vect_recog_rotate_pattern /home/seurer/gcc/git/gcc-test/gcc/tree-vect-patterns.cc:3634 0x11b9cdeb vect_pattern_recog_1 /home/seurer/gcc/git/gcc-test/gcc/tree-vect-patterns.cc:6834 0x11ba5387 vect_pattern_recog(vec_info*) /home/seurer/gcc/git/gcc-test/gcc/tree-vect-patterns.cc:6991 0x110a001f vect_slp_analyze_bb_1 /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.cc:7353 0x110a001f vect_slp_region /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.cc:7462 0x110a2733 vect_slp_bbs /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.cc:7653 0x110a2b7b vect_slp_function(function*) /home/seurer/gcc/git/gcc-test/gcc/tree-vect-slp.cc:7754 0x110b1b73 execute /home/seurer/gcc/git/gcc-test/gcc/tree-vectorizer.cc:1529
next prev parent reply other threads:[~2023-06-28 22:20 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-28 16:46 [Bug tree-optimization/110461] New: " sjames at gcc dot gnu.org 2023-06-28 16:51 ` [Bug tree-optimization/110461] " pinskia at gcc dot gnu.org 2023-06-28 16:51 ` pinskia at gcc dot gnu.org 2023-06-28 17:29 ` sjames at gcc dot gnu.org 2023-06-28 17:39 ` pinskia at gcc dot gnu.org 2023-06-28 17:44 ` pinskia at gcc dot gnu.org 2023-06-28 17:51 ` pinskia at gcc dot gnu.org 2023-06-28 19:07 ` pinskia at gcc dot gnu.org 2023-06-28 22:16 ` dcb314 at hotmail dot com 2023-06-28 22:19 ` pinskia at gcc dot gnu.org 2023-06-28 22:20 ` seurer at gcc dot gnu.org [this message] 2023-06-29 4:03 ` pinskia at gcc dot gnu.org 2023-06-29 7:13 ` rguenth at gcc dot gnu.org 2023-06-29 7:13 ` rguenth at gcc dot gnu.org 2023-06-29 7:43 ` dcb314 at hotmail dot com 2023-06-29 8:14 ` cvs-commit at gcc dot gnu.org 2023-06-29 8:14 ` 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-110461-4-z9f41yOhOM@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).