public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com> To: Richard Biener <richard.guenther@gmail.com> Cc: Andrew Stubbs <ams@codesourcery.com>, "gcc-regression@gcc.gnu.org" <gcc-regression@gcc.gnu.org>, "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>, "haochen.jiang@intel.com" <haochen.jiang@intel.com> Subject: Re: [r13-7135 Regression] FAIL: gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 on Linux/x86_64 Date: Fri, 14 Apr 2023 09:43:25 +0100 [thread overview] Message-ID: <a25f3928-da31-8010-67d1-aaf48a3376b7@arm.com> (raw) In-Reply-To: <CAFiYyc3=DzNiGmkobfojhS09NEDVnrmC35pMV07SyGHiwk6Vkw@mail.gmail.com> Resending this to everyone (sorry for the double send Richard). On 14/04/2023 09:15, Andre Vieira (lists) wrote: > > > On 14/04/2023 07:55, Richard Biener wrote: >> On Thu, Apr 13, 2023 at 4:25 PM Andre Vieira (lists) >> <andre.simoesdiasvieira@arm.com> wrote: >>> >>> >>> >>> On 13/04/2023 15:00, Richard Biener wrote: >>>> On Thu, Apr 13, 2023 at 3:00 PM Andre Vieira (lists) via Gcc-patches >>>> <gcc-patches@gcc.gnu.org> wrote: >>>>> >>>>> >>>>> >>> >>> But that's not it, I've been looking at it, and there is code in place >>> that does what I expected which is defer the choice of vectype for simd >>> clones until vectorizable_simd_clone_call, unfortunately it has a >>> mistaken assumption that simdclones don't return :/ >> >> I think that's not it - when the SIMD clone returns a vector we have to >> determine the vector type in this function. We cannot defer this. > > What's 'this function' here, do you mean we have to determine the > vectype in 'vect_get_vector_types_for_stmt' & > 'vect_determine_vf_for_stmt' ? Because at that time we don't yet know > what clone we will be using, this choice is done inside > vectorizable_simd_clone_call. In fact, to choose the simd clone, we need > to know the vf as that has to be a multiple of the chosen clone's > simdlen. So we simply can't use the simdclone's types (as that depends > on the simdlen) to choose the vf because the choice of simdlend depends > on the vf. And there was already code in place to handle this, > unfortunately that code was wrong and had the wrong assumption that > simdclones didn't return (probably was true at some point and bitrotted). > >> >>> see vect_get_vector_types_for_stmt: >>> ... >>> if (gimple_get_lhs (stmt) == NULL_TREE >>> /* MASK_STORE has no lhs, but is ok. */ >>> && !gimple_call_internal_p (stmt, IFN_MASK_STORE)) >>> { >>> if (is_a <gcall *> (stmt)) >>> { >>> /* Ignore calls with no lhs. These must be calls to >>> #pragma omp simd functions, and what vectorization factor >>> it really needs can't be determined until >>> vectorizable_simd_clone_call. */ >>> if (dump_enabled_p ()) >>> dump_printf_loc (MSG_NOTE, vect_location, >>> "defer to SIMD clone analysis.\n"); >>> return opt_result::success (); >>> } >>> >>> return opt_result::failure_at (stmt, >>> "not vectorized: irregular >>> stmt.%G", stmt); >>> } >>> ... >>> >>> I'm working on a patch. >>>> >>>>> Kind Regards, >>>>> Andre
next prev parent reply other threads:[~2023-04-14 8:43 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 1:48 haochen.jiang 2023-04-13 9:15 ` Andre Simoes Dias Vieira 2023-04-13 10:01 ` Andrew Stubbs 2023-04-13 12:59 ` Andre Vieira (lists) 2023-04-13 14:00 ` Richard Biener 2023-04-13 14:25 ` Andre Vieira (lists) 2023-04-14 6:55 ` Richard Biener 2023-04-14 8:43 ` Andre Vieira (lists) [this message] 2023-04-14 9:09 ` Richard Biener 2023-04-14 9:14 ` Richard Biener 2023-04-14 9:42 ` Andre Vieira (lists) 2023-04-14 11:47 ` Richard Biener 2023-04-14 12:57 ` Andre Vieira (lists)
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=a25f3928-da31-8010-67d1-aaf48a3376b7@arm.com \ --to=andre.simoesdiasvieira@arm.com \ --cc=ams@codesourcery.com \ --cc=gcc-patches@gcc.gnu.org \ --cc=gcc-regression@gcc.gnu.org \ --cc=haochen.jiang@intel.com \ --cc=richard.guenther@gmail.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: linkBe 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).