public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104935] [12 Regression] 554.roms_r ELF binary increased with r12-7612-g69619acd8d9b5856
Date: Wed, 16 Mar 2022 15:03:11 +0000	[thread overview]
Message-ID: <bug-104935-4-qzL8cU9FR8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104935-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So in 554.roms_r I see cases (like for mod_grid.F90:allocate_grid) where
we now vectorize more V4DI stores from a CTOR of scalars which reduces code
size so jump-threading now goes wild (from DOM threading), threading across
the long repetition of

  if (div == 0)
    ;
  else
    ... = ... / div;


  <vectorized blob>
  if (div == 0)
    ;
  else
    ... = ... / div;

where the vectorized blob is now smaller than the threading threshold.

For extract_sta.F90 we now vectorize two more loops with low VF (high VF
is not profitable) but using only strided loads (they are reductions)
which has extra size cost on the scalar epilogues plus we are vectorizing
conditional reductions here.  It doesn't look overly bad here.

There's also a TU with a size win btw, but overall we vectorize more.

  parent reply	other threads:[~2022-03-16 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 12:15 [Bug tree-optimization/104935] New: " marxin at gcc dot gnu.org
2022-03-15 12:25 ` [Bug tree-optimization/104935] " rguenth at gcc dot gnu.org
2022-03-15 12:56 ` marxin at gcc dot gnu.org
2022-03-16 15:03 ` rguenth at gcc dot gnu.org [this message]
2022-05-06  8:33 ` [Bug tree-optimization/104935] [12/13 " jakub at gcc dot gnu.org
2022-07-26 12:42 ` 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-104935-4-qzL8cU9FR8@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).