public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	 Richard Sandiford <richard.sandiford@arm.com>,
	 Jeff Law <jlaw@ventanamicro.com>
Subject: Re: [PATCH] ifcvt: Do not lower bitfields if we can't analyze dr's [PR107275]
Date: Tue, 18 Oct 2022 09:01:15 +0000 (UTC)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2210180901060.18337@jbgna.fhfr.qr> (raw)
In-Reply-To: <0888cc2d-2040-52c3-1201-16400567300b@arm.com>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

On Tue, 18 Oct 2022, Andre Vieira (lists) wrote:

> The ifcvt dead code elimination code was not built to deal with inline
> assembly, as loops with such would never be if-converted in the past since
> we can't do data-reference analysis on them and vectorization would eventually
> fail.
> For this reason we now also do not lower bitfields if the data-reference
> analysis
> fails, as we would not end up vectorizing it.  As a consequence this also
> fixes
> this PR as the dead code elimination will not run for such cases and
> wrongfully
> eliminate inline assembly statements.
> 
> Bootstrapped and regression tested on aarch64-none-linux-gnu and
> x86_64-pc-linux-gnu.

OK.

Thanks,
Richard.

> gcc/ChangeLog:
> 
>     PR tree-optimization/107275
>     * tree-if-conv.cc (if_convertible_loop_p_1): Move
>     find_data_references_in_loop call from here...
>     (if_convertible_loop_p): And move data-reference vector initialization
>     from here...
>     (tree_if_conversion):... to here.
> 
> gcc/testsuite/ChangeLog:
> 
>     * gcc.dg/vect/pr107275.c: New test.
> 

-- 
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg,
Germany; GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman;
HRB 36809 (AG Nuernberg)

      reply	other threads:[~2022-10-18  9:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  8:35 Andre Vieira (lists)
2022-10-18  9:01 ` 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=nycvar.YFH.7.77.849.2210180901060.18337@jbgna.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=andre.simoesdiasvieira@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jlaw@ventanamicro.com \
    --cc=richard.sandiford@arm.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).