public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98854] [11 Regression] cray benchmark is about 15% slower since r11-4428-g4a369d199bf2f34e
Date: Wed, 27 Jan 2021 15:17:30 +0000	[thread overview]
Message-ID: <bug-98854-4-t4AFjvAAVu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98854-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98854

--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 27 Jan 2021, marxin at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98854
> 
> --- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
> > I used -O3 but -O2 -ftree-slp-vectorize also vectorizes it.
> 
> I must be blind, but I see for the current master:
> 
> gcc pr98854.c -c -O2 -ftree-slp-vectorize -fdump-tree-optimized=/dev/stdout
> 
> foo (int n)
> {
>   unsigned long ivtmp.8;
>   double y;
>   double x;
>   double _6;
>   double _8;
>   double _9;
>   double _11;
>   int _14;
>   void * _29;
>   unsigned long _31;
> 
>   <bb 2>:
>   ivtmp.8_28 = (unsigned long) &MEM[(void *)&a + 8184B];
>   _31 = (unsigned long) &a;
> 
>   <bb 3>:
>   # x_1 = PHI <0.0(2), x_10(5)>
>   # y_2 = PHI <0.0(2), y_12(5)>
>   # ivtmp.8_18 = PHI <ivtmp.8_28(2), ivtmp.8_27(5)>
>   _29 = (void *) ivtmp.8_18;
>   _6 = MEM[base: _29, offset: 0B];
>   _8 = MEM[base: _29, offset: 8B];
>   _9 = _6 + _8;
>   x_10 = _9 + x_1;
>   _11 = _6 / _8;
>   y_12 = _11 + y_2;
>   _14 = bar ();
>   if (_14 != 0)
>     goto <bb 4>;
>   else
>     goto <bb 5>;
> 
>   <bb 4>:
>   a[0] = x_10;
>   a[1] = y_12;
>   return;
> 
>   <bb 5>:
>   ivtmp.8_27 = ivtmp.8_18 - 8;
>   if (ivtmp.8_27 != _31)
>     goto <bb 3>;
>   else
>     goto <bb 4>;
> 
> }

Hmm, maybe my dev tree has related adjustments to SLP ... at least
the posted patch fixes the regression for me.

  parent reply	other threads:[~2021-01-27 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 12:45 [Bug tree-optimization/98854] New: " marxin at gcc dot gnu.org
2021-01-27 12:46 ` [Bug tree-optimization/98854] " marxin at gcc dot gnu.org
2021-01-27 13:13 ` rguenth at gcc dot gnu.org
2021-01-27 13:46 ` rguenth at gcc dot gnu.org
2021-01-27 14:22 ` rguenth at gcc dot gnu.org
2021-01-27 14:39 ` marxin at gcc dot gnu.org
2021-01-27 14:45 ` rguenther at suse dot de
2021-01-27 14:52 ` marxin at gcc dot gnu.org
2021-01-27 15:17 ` rguenther at suse dot de [this message]
2021-01-27 16:33 ` cvs-commit at gcc dot gnu.org
2021-01-27 16:34 ` rguenth at gcc dot gnu.org

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-98854-4-t4AFjvAAVu@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: 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).