public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/110506] New: ice: tree check: expected none of vector_type, have vector_type in get_value_for_expr, at tree-ssa-ccp.cc:686 Date: Fri, 30 Jun 2023 17:43:20 +0000 [thread overview] Message-ID: <bug-110506-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110506 Bug ID: 110506 Summary: ice: tree check: expected none of vector_type, have vector_type in get_value_for_expr, at tree-ssa-ccp.cc:686 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this C code: struct { long *sp; long *csp } neko_interp_loop_vm; int neko_interp_loop_vm_2; void neko_interp_loop() { long pc[] = {&&LabelAccGlobal, &&LabelPhysCompare, &&LabelTailCall, &&LabelLoop, &&LabelMakeArray2}; long *sp, *csp = neko_interp_loop_vm.csp; LabelAccGlobal: neko_interp_loop_vm.sp = sp; neko_interp_loop_vm.csp = csp; goto * 0; LabelTailCall: csp = sp -= neko_interp_loop_vm_2; LabelMakeArray2: LabelPhysCompare: LabelLoop: goto * 0; } compiled by g:9757e4440bd8755d, does this: $ ~/gcc/results.20230628.asan.ubsan/bin/gcc -c -w -O2 bug936.c during GIMPLE pass: ccp /home/dcb38/rpmbuild/BUILD/neko-2-3-0/vm/interp.c: In function ‘neko_interp_loop’: /home/dcb38/rpmbuild/BUILD/neko-2-3-0/vm/interp.c:613:9: internal compiler error: tree check: expected none of vector_type, have vector_type in get_value_for_expr, at tree-ssa-ccp.cc:686 613 | int_val neko_interp_loop( neko_vm *VM_ARG, neko_module *m, int_val _acc, int_val *_pc ) { | ^~~~~~~~~~~~~~~~ 0x11656f9 tree_not_check_failed(tree_node const*, char const*, int, char const*, ...) ../../trunk.year/gcc/tree.cc:8936 0xf75774 tree_not_check(tree_node*, char const*, int, char const*, tree_code) ../../trunk.year/gcc/tree.h:3581 0xf75774 get_value_for_expr(tree_node*, bool) ../../trunk.year/gcc/tree-ssa-ccp.cc:686 It was fine with a version from a couple of days earlier: foundBugs $ ~/gcc/results.20230626.asan.ubsan/bin/gcc -c -w -O2 bug936.c foundBugs $ ~/gcc/results.20230626.asan.ubsan/bin/gcc -v Using built-in specs. COLLECT_GCC=/home/dcb38/gcc/results.20230626.asan.ubsan/bin/gcc COLLECT_LTO_WRAPPER=/home/dcb38/gcc/results.20230626.asan.ubsan/libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../trunk.year/configure --prefix=/home/dcb38/gcc/results.20230626.asan.ubsan --disable-multilib --disable-bootstrap --with-build-config=bootstrap-asan --with-build-config=bootstrap-ubsan --with-pkgversion=3a39a31b8ae9c646 --enable-checking=df,extra,fold,rtl,yes --enable-languages=c,c++,fortran Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.0 20230626 (experimental) (3a39a31b8ae9c646)
next reply other threads:[~2023-06-30 17:43 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-30 17:43 dcb314 at hotmail dot com [this message] 2023-06-30 19:31 ` [Bug tree-optimization/110506] [14 Regression] Ice: " pinskia at gcc dot gnu.org 2023-06-30 19:38 ` pinskia at gcc dot gnu.org 2023-06-30 20:13 ` pinskia at gcc dot gnu.org 2023-06-30 20:14 ` pinskia at gcc dot gnu.org 2023-07-01 8:15 ` dcb314 at hotmail dot com 2023-07-03 6:25 ` rguenth at gcc dot gnu.org 2023-07-03 8:05 ` cvs-commit at gcc dot gnu.org 2023-07-03 8:05 ` cvs-commit at gcc dot gnu.org 2023-07-03 8:06 ` 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-110506-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).