public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "141242068 at smail dot nju.edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/112505] New: GCC: 14: internal compiler error: in build_vector_from_val, at tree.cc:2104
Date: Mon, 13 Nov 2023 03:45:15 +0000 [thread overview]
Message-ID: <bug-112505-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112505
Bug ID: 112505
Summary: GCC: 14: internal compiler error: in
build_vector_from_val, at tree.cc:2104
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: 141242068 at smail dot nju.edu.cn
Target Milestone: ---
Compiler Explorer: https://gcc.godbolt.org/z/nTjnh73xj
The crash triggering program (compile with `gcc-14 -O3`):
```
short int w9;
struct T {
short a : 14;
int b;
};
struct T v;
void __attribute__((simd)) zc() {
w9 *= v.b ? v.a-- < 0 : 0;
}
```
The crash output:
```
during GIMPLE pass: vect
<source>: In function 'zc.simdclone.0':
<source>:7:28: internal compiler error: in build_vector_from_val, at
tree.cc:2104
7 | void __attribute__((simd)) zc() {
| ^~
0x238b15e internal_error(char const*, ...)
???:0
0xa11270 fancy_abort(char const*, int, char const*)
???:0
0x13ee023 vectorizable_induction(_loop_vec_info*, _stmt_vec_info*, gimple**,
_slp_tree*, vec<stmt_info_for_cost, va_heap, vl_ptr>*)
???:0
0x2115bf8 vect_transform_stmt(vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*)
???:0
0x13fedc0 vect_transform_loop(_loop_vec_info*, gimple*)
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1
```
next reply other threads:[~2023-11-13 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 3:45 141242068 at smail dot nju.edu.cn [this message]
2023-11-13 6:10 ` [Bug tree-optimization/112505] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-11-13 6:11 ` pinskia at gcc dot gnu.org
2023-11-13 9:32 ` rguenth at gcc dot gnu.org
2023-12-07 9:53 ` [Bug tree-optimization/112505] [11/12/13/14 Regression] internal compiler error: in build_vector_from_val, at tree.cc:2104 since r10-4076 jakub at gcc dot gnu.org
2024-01-11 13:08 ` rguenth at gcc dot gnu.org
2024-01-11 14:13 ` cvs-commit at gcc dot gnu.org
2024-02-06 13:20 ` [Bug tree-optimization/112505] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-17 11:12 ` [Bug tree-optimization/112505] [11/12 " cvs-commit at gcc dot gnu.org
2024-06-21 9:22 ` [Bug tree-optimization/112505] [11 " cvs-commit at gcc dot gnu.org
2024-06-21 9:37 ` 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-112505-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: link
Be 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).