public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113163] New: [14 Regression][GCN] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 Date: Thu, 28 Dec 2023 11:37:57 +0000 [thread overview] Message-ID: <bug-113163-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113163 Bug ID: 113163 Summary: [14 Regression][GCN] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: tamar.christina at arm dot com Target Milestone: --- Target: amdgcn-amdhsa The ICE happens when building Newlib with the GCN compiler: during GIMPLE pass: vect In file included from src/accel_newlib-mainline/newlib/libc/stdlib/l64a.c:24: src/accel_newlib-mainline/newlib/libc/include/stdlib.h: In function 'l64a': src/accel_newlib-mainline/newlib/libc/include/stdlib.h:195:9: internal compiler error: in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9420 195 | char * l64a (long __input); | ^~~~
next reply other threads:[~2023-12-28 11:37 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-28 11:37 burnus at gcc dot gnu.org [this message] 2023-12-28 11:53 ` [Bug middle-end/113163] " tnfchris at gcc dot gnu.org 2023-12-28 12:20 ` burnus at gcc dot gnu.org 2023-12-28 12:22 ` tnfchris at gcc dot gnu.org 2023-12-28 12:25 ` tnfchris at gcc dot gnu.org 2023-12-28 12:27 ` burnus at gcc dot gnu.org 2023-12-28 12:30 ` burnus at gcc dot gnu.org 2023-12-28 14:20 ` tnfchris at gcc dot gnu.org 2023-12-28 14:20 ` tnfchris at gcc dot gnu.org 2023-12-29 14:48 ` tnfchris at gcc dot gnu.org 2023-12-29 21:06 ` tnfchris at gcc dot gnu.org 2024-01-02 11:29 ` ams at gcc dot gnu.org 2024-01-02 11:35 ` tnfchris at gcc dot gnu.org 2024-01-06 6:14 ` pinskia at gcc dot gnu.org 2024-01-09 11:18 ` cvs-commit at gcc dot gnu.org 2024-01-09 11:25 ` tnfchris 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-113163-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).