public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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, 09 Jan 2024 13:39:17 +0000 [thread overview] Message-ID: <bug-113199-4-QYvu1ngUvP@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 --- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:80bb94e88faaadd4d6f008fececb46214dc89e9f commit r14-7065-g80bb94e88faaadd4d6f008fececb46214dc89e9f Author: Tamar Christina <tamar.christina@arm.com> Date: Tue Jan 9 13:35:49 2024 +0000 middle-end: check if target can do extract first for early breaks [PR113199] I was generating the vector reverse mask without checking if the target actually supported such an operation. This patch changes it to if the bitstart is 0 then use BIT_FIELD_REF instead to extract the first element since this is supported by all targets. This is good for now since masks always come from whilelo. But in the future when masks can come from other sources we will need the old code back. gcc/ChangeLog: PR tree-optimization/113199 * tree-vect-loop.cc (vectorizable_live_operation_1): Use BIT_FIELD_REF. gcc/testsuite/ChangeLog: PR tree-optimization/113199 * gcc.target/gcn/pr113199.c: New test.
next prev parent reply other threads:[~2024-01-09 13:39 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 ` [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-02 17:58 ` 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 [this message] 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-QYvu1ngUvP@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).