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 target/105209] internal compiler error: in store_data_bypass_p_1 Date: Fri, 17 Jun 2022 15:21:03 +0000 [thread overview] Message-ID: <bug-105209-4-6HlDtDarq8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105209-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105209 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:cc378e655740e93743e7f43e14faaff707aef6c1 commit r13-1157-gcc378e655740e93743e7f43e14faaff707aef6c1 Author: Uros Bizjak <ubizjak@gmail.com> Date: Fri Jun 17 17:19:44 2022 +0200 alpha: Introduce target specific store_data_bypass_p function [PR105209] This patch introduces alpha-specific version of store_data_bypass_p that ignores TRAP_IF that would result in assertion failure (and internal compiler error) in the generic store_data_bypass_p function. While at it, also remove ev4_ist_c reservation, store_data_bypass_p can handle the patterns with multiple sets since some time ago. 2022-06-17 Uroš Bizjak <ubizjak@gmail.com> gcc/ChangeLog: PR target/105209 * config/alpha/alpha-protos.h (alpha_store_data_bypass_p): New. * config/alpha/alpha.cc (alpha_store_data_bypass_p): New function. (alpha_store_data_bypass_p_1): Ditto. * config/alpha/ev4.md: Use alpha_store_data_bypass_p instead of generic store_data_bypass_p. (ev4_ist_c): Remove insn reservation. gcc/testsuite/ChangeLog: PR target/105209 * gcc.target/alpha/pr105209.c: New test.
next prev parent reply other threads:[~2022-06-17 15:21 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-10 19:51 [Bug c/105209] New: " roland.illig at gmx dot de 2022-04-11 7:29 ` [Bug target/105209] " rguenth at gcc dot gnu.org 2022-04-11 11:48 ` ubizjak at gmail dot com 2022-06-17 15:21 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-20 18:47 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:46 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:53 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:54 ` ubizjak at gmail dot com
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-105209-4-6HlDtDarq8@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).