public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/113199] [14 Regression][GCN] ICE (segfault) due to invalid 'loop_mask_46 = VEC_PERM_EXPR' when compiling Newlib's wcsftime.c Date: Tue, 02 Jan 2024 15:28:24 +0000 [thread overview] Message-ID: <bug-113199-4-KSydbpH8n7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113199-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113199 Tamar Christina <tnfchris at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-01-02 Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> --- Thanks, patch for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113137 will reject this function since it's not safe to vectorize. For this is looks like I has assumed the target could reverse a mask and didn't check. I'll add a check.
next prev parent reply other threads:[~2024-01-02 15:28 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 14:14 [Bug middle-end/113199] New: [14 Regression][GCN] ICE (segfault) when compiling Newlib burnus at gcc dot gnu.org 2024-01-02 15:28 ` tnfchris at gcc dot gnu.org [this message] 2024-01-02 17:58 ` [Bug middle-end/113199] [14 Regression][GCN] ICE (segfault) due to invalid 'loop_mask_46 = VEC_PERM_EXPR' when compiling Newlib's wcsftime.c tnfchris at gcc dot gnu.org 2024-01-06 6:14 ` pinskia at gcc dot gnu.org 2024-01-09 13:39 ` cvs-commit at gcc dot gnu.org 2024-01-09 13:45 ` tnfchris at gcc dot gnu.org 2024-01-09 14:08 ` ams 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-113199-4-KSydbpH8n7@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).