From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [PATCH 0/3] arm: Fix regressions around MVE predicate codegen
Date: Tue, 24 Jan 2023 13:31:48 +0000 [thread overview]
Message-ID: <13d03aef-f5d1-03fe-5281-31921d24dce0@arm.com> (raw)
Hi all,
This patch series aims to fix two or three (depends on how you look at
it) regressions that came about in gcc 11. The first and third patch
address wrong-codegen regressions and the second a performance
regression. Patch two makes a change to the mid-end so I can understand
if there are reservations about making these changes this late in the
development stage, unfortunately I didn't get around to fixing them earlier.
Andre Vieira (3):
arm: Fix sign of MVE predicate mve_pred16_t [PR 107674]
arm: Remove unnecessary zero-extending of MVE predicates before use [PR
107674]
arm: Fix MVE predicates synthesis [PR 108443]
next reply other threads:[~2023-01-24 13:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 13:31 Andre Vieira (lists) [this message]
2023-01-24 13:40 ` [PATCH 1/3] arm: Fix sign of MVE predicate mve_pred16_t [PR 107674] Andre Vieira (lists)
2023-01-24 13:48 ` Andre Vieira (lists)
2023-01-26 15:02 ` Kyrylo Tkachov
2023-01-26 15:03 ` Kyrylo Tkachov
2023-01-27 9:54 ` Andre Vieira (lists)
2023-01-27 9:56 ` Kyrylo Tkachov
2023-01-30 16:38 ` Andre Vieira (lists)
2023-01-30 16:40 ` Kyrylo Tkachov
2023-01-24 13:54 ` [PATCH 2/3] arm: Remove unnecessary zero-extending of MVE predicates before use " Andre Vieira (lists)
2023-01-26 15:06 ` Kyrylo Tkachov
2023-01-27 9:58 ` Andre Vieira (lists)
2023-01-27 9:59 ` Kyrylo Tkachov
2023-01-30 16:41 ` Andre Vieira (lists)
2023-01-30 23:17 ` Richard Sandiford
2023-01-31 6:15 ` Richard Sandiford
2023-01-24 13:56 ` [PATCH 3/3] arm: Fix MVE predicates synthesis [PR 108443] Andre Vieira (lists)
2023-01-25 17:40 ` Andre Vieira (lists)
2023-01-31 9:53 ` Kyrylo Tkachov
2023-01-31 11:38 ` Andre Vieira (lists)
2023-01-31 16:44 ` Kyrylo Tkachov
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=13d03aef-f5d1-03fe-5281-31921d24dce0@arm.com \
--to=andre.simoesdiasvieira@arm.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).