public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4227] tree-optimization/107672 - avoid vector mode type_for_mode call
Date: Tue, 22 Nov 2022 08:49:08 +0000 (GMT)	[thread overview]
Message-ID: <20221122084908.283CC3858022@sourceware.org> (raw)

https://gcc.gnu.org/g:09b7993ab6d93716f77c03ff9a9165fa4b579f0d

commit r13-4227-g09b7993ab6d93716f77c03ff9a9165fa4b579f0d
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Nov 22 09:03:53 2022 +0100

    tree-optimization/107672 - avoid vector mode type_for_mode call
    
    The following avoids using type_for_mode on vector modes which might
    not work for all frontends.  Instead we look for the inner mode
    type and use build_vector_type_for_mode instead.
    
            PR tree-optimization/107672
            * tree-vect-stmts.cc (supportable_widening_operation): Avoid
            type_for_mode on vector modes.

Diff:
---
 gcc/tree-vect-stmts.cc | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc
index bc0ef136f19..b35b986889d 100644
--- a/gcc/tree-vect-stmts.cc
+++ b/gcc/tree-vect-stmts.cc
@@ -12195,9 +12195,15 @@ supportable_widening_operation (vec_info *vinfo,
 	intermediate_type
 	  = vect_halve_mask_nunits (prev_type, intermediate_mode);
       else
-	intermediate_type
-	  = lang_hooks.types.type_for_mode (intermediate_mode,
-					    TYPE_UNSIGNED (prev_type));
+	{
+	  gcc_assert (VECTOR_MODE_P (intermediate_mode));
+	  tree intermediate_element_type
+	    = lang_hooks.types.type_for_mode (GET_MODE_INNER (intermediate_mode),
+					      TYPE_UNSIGNED (prev_type));
+	  intermediate_type
+	    = build_vector_type_for_mode (intermediate_element_type,
+					  intermediate_mode);
+	}
 
       if (VECTOR_BOOLEAN_TYPE_P (intermediate_type)
 	  && VECTOR_BOOLEAN_TYPE_P (prev_type)

                 reply	other threads:[~2022-11-22  8:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221122084908.283CC3858022@sourceware.org \
    --to=rguenth@gcc.gnu.org \
    --cc=gcc-cvs@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).