This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[0/4] Vector epilogues vs. mixed vector sizes

From: Richard Sandiford <richard dot sandiford at arm dot com>
To: gcc-patches at gcc dot gnu dot org
Cc: andre dot simoesdiasvieira at arm dot com
Date: Mon, 04 Nov 2019 15:23:07 +0000
Subject: [0/4] Vector epilogues vs. mixed vector sizes

This patch bridges the gap between the recent epilogue vectorisation
patches and https://gcc.gnu.org/ml/gcc-patches/2019-10/msg01822.html .
I don't have any evidence that the series is independently useful,
but it shouldn't make things worse either.

Tested individually on aarch64-linux-gnu and as a series on
x86_64-linux-gnu.  OK to install?

Richard

Follow-Ups:
- [1/4] Restructure vect_analyze_loop
  - From: Richard Sandiford
- [2/4] Check the VF is small enough for an epilogue loop
  - From: Richard Sandiford
- [3/4] Don't vectorise single-iteration epilogues
  - From: Richard Sandiford
- [4/4] Use scan-tree-dump instead of scan-tree-dump-times for some vect tests
  - From: Richard Sandiford

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]