From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] alpha: Introduce target specific store_data_bypass_p function [PR105209]
Date: Fri, 17 Jun 2022 14:12:40 -0600 [thread overview]
Message-ID: <02253d73-9b14-d971-43ec-8be86aa516ed@gmail.com> (raw)
In-Reply-To: <CAFULd4Zde24D0t300FoSGyJ63zY57ySmB-XC41tD8FWYwkvTXg@mail.gmail.com>
On 6/17/2022 9:22 AM, Uros Bizjak via Gcc-patches wrote:
> 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.
>
> Tested with a cross-compiler.
>
> Pushed to master
And FWIW it'll get bootstrapped using qemu user mode emulation over the
weekend.
http://law-sandy.freeddns.org:8080/job/alpha-linux-gnu
jeff
ps. I think last weekend's run got aborted due to an overheated server.
prev parent reply other threads:[~2022-06-17 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 15:22 Uros Bizjak
2022-06-17 20:12 ` Jeff Law [this message]
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=02253d73-9b14-d971-43ec-8be86aa516ed@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).