public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114464] New: [14 regression] ICE when building tdscpp-20240212 Date: Mon, 25 Mar 2024 12:12:23 +0000 [thread overview] Message-ID: <bug-114464-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114464 Bug ID: 114464 Summary: [14 regression] ICE when building tdscpp-20240212 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org Target Milestone: --- Created attachment 57808 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57808&action=edit bcp.cpp.ii.xz ``` $ g++ -c bcp.cpp.ii -O2 -std=gnu++23 /var/tmp/portage/dev-db/tdscpp-20240212/work/tdscpp-20240212/src/bcp.cpp: In function ‘void tds::bcp_row_data(uint8_t*&, const col_info&, const value&, std::u16string_view)’: /var/tmp/portage/dev-db/tdscpp-20240212/work/tdscpp-20240212/src/bcp.cpp:578:10: error: incompatible types in ‘PHI’ argument 0 578 | void bcp_row_data(uint8_t*& ptr, const col_info& col, const value& vv, u16string_view col_name) { | ^~~~~~~~~~~~ vector(16) unsigned char vector(16) <signed-boolean:8> vect_vec_recur_.4107_221 = PHI <mask_b_306.4112_2569(835), { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }(831)> /var/tmp/portage/dev-db/tdscpp-20240212/work/tdscpp-20240212/src/bcp.cpp:578:10: error: type mismatch in ‘vec_perm_expr’ vector(16) unsigned char vector(16) unsigned char vector(16) <signed-boolean:8> vector(16) ssizetype _2739 = VEC_PERM_EXPR <vect_vec_recur_.4107_221, mask_b_306.4112_2569, { 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 }>; during GIMPLE pass: vect /var/tmp/portage/dev-db/tdscpp-20240212/work/tdscpp-20240212/src/bcp.cpp:578:10: internal compiler error: verify_gimple failed 0x558d86f1abae verify_gimple_in_cfg(function*, bool, bool) /usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/tree-cfg.cc:5663 0x558d886683f4 execute_function_todo /usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:2088 0x558d886683f4 do_per_function /usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:1687 0x558d886683f4 execute_todo /usr/src/debug/sys-devel/gcc-14.0.9999/gcc-14.0.9999/gcc/passes.cc:2142 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://bugs.gentoo.org/> for instructions. ```
next reply other threads:[~2024-03-25 12:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-25 12:12 sjames at gcc dot gnu.org [this message] 2024-03-25 12:32 ` [Bug tree-optimization/114464] " rguenth at gcc dot gnu.org 2024-03-25 12:33 ` sjames at gcc dot gnu.org 2024-03-25 21:33 ` sjames at gcc dot gnu.org 2024-03-25 21:51 ` xry111 at gcc dot gnu.org 2024-03-25 23:13 ` pinskia at gcc dot gnu.org 2024-03-25 23:15 ` pinskia at gcc dot gnu.org 2024-03-26 8:22 ` rguenth at gcc dot gnu.org 2024-03-26 9:38 ` cvs-commit at gcc dot gnu.org 2024-03-26 9:44 ` 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-114464-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).