From: Richard Biener <richard.guenther@gmail.com>
To: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-ssa-loop-prefetch.cc: Honour -fno-unroll-loops
Date: Wed, 8 May 2024 10:32:55 +0200 [thread overview]
Message-ID: <CAFiYyc1dH=jsMQNzTftcmRSSNU_i7LGY8X=kT2FeBEreyr50oA@mail.gmail.com> (raw)
In-Reply-To: <20240508075457.1243150-1-stefansf@linux.ibm.com>
On Wed, May 8, 2024 at 9:56 AM Stefan Schulze Frielinghaus
<stefansf@linux.ibm.com> wrote:
>
> On s390 the following tests fail
>
> FAIL: gcc.dg/vect/pr109011-1.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .CLZ \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-1.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-1.c scan-tree-dump-times optimized " = .CLZ \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-1.c scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-2.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .CTZ \\\\(vect" 2
> FAIL: gcc.dg/vect/pr109011-2.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-2.c scan-tree-dump-times optimized " = .CTZ \\\\(vect" 2
> FAIL: gcc.dg/vect/pr109011-2.c scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-4.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .CTZ \\\\(vect" 2
> FAIL: gcc.dg/vect/pr109011-4.c -flto -ffat-lto-objects scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
> FAIL: gcc.dg/vect/pr109011-4.c scan-tree-dump-times optimized " = .CTZ \\\\(vect" 2
> FAIL: gcc.dg/vect/pr109011-4.c scan-tree-dump-times optimized " = .POPCOUNT \\\\(vect" 1
>
> because aprefetch unrolls loops even if -fno-unroll-loops is used.
> Accordingly, the scan patterns match more than one time.
>
> Could also be fixed by using -fno-prefetch-loop-arrays for the tests.
> Though, I tend to prefer if aprefetch honours -fno-unroll-loops. Any
> preferences?
>
> Bootstrapped and regtested on x86_64 and s390. Ok for mainline?
OK.
Richard.
> gcc/ChangeLog:
>
> * tree-ssa-loop-prefetch.cc (determine_unroll_factor): Honour
> -fno-unroll-loops.
> ---
> gcc/tree-ssa-loop-prefetch.cc | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/gcc/tree-ssa-loop-prefetch.cc b/gcc/tree-ssa-loop-prefetch.cc
> index 70073cc4fe4..bb5d5dec779 100644
> --- a/gcc/tree-ssa-loop-prefetch.cc
> +++ b/gcc/tree-ssa-loop-prefetch.cc
> @@ -1401,6 +1401,10 @@ determine_unroll_factor (class loop *loop, struct mem_ref_group *refs,
> struct mem_ref_group *agp;
> struct mem_ref *ref;
>
> + /* Bail out early in case we must not unroll loops. */
> + if (!flag_unroll_loops)
> + return 1;
> +
> /* First check whether the loop is not too large to unroll. We ignore
> PARAM_MAX_UNROLL_TIMES, because for small loops, it prevented us
> from unrolling them enough to make exactly one cache line covered by each
> --
> 2.44.0
>
prev parent reply other threads:[~2024-05-08 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 7:54 Stefan Schulze Frielinghaus
2024-05-08 8:32 ` Richard Biener [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='CAFiYyc1dH=jsMQNzTftcmRSSNU_i7LGY8X=kT2FeBEreyr50oA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=stefansf@linux.ibm.com \
/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).