public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105254] ICE in exact_div, at poly-int.h:2219 Date: Wed, 13 Apr 2022 16:54:06 +0000 [thread overview] Message-ID: <bug-105254-4-NmNhUBx4j2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105254-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105254 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>: https://gcc.gnu.org/g:f2ebf2d98efe0ac2314b58cf474f44cb8ebd5244 commit r12-8146-gf2ebf2d98efe0ac2314b58cf474f44cb8ebd5244 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Wed Apr 13 17:53:54 2022 +0100 aarch64: Make sure the UF divides the VF [PR105254] In this PR, we were trying to set the unroll factor to a value higher than the minimum VF (or more specifically, to a value that doesn't divide the VF). I guess there are two approaches to this: let the target pick any value it likes and make target-independent code pare it back to something that makes sense, or require targets to supply sensible values from the outset. This patch goes for the latter approach. gcc/ PR tree-optimization/105254 * config/aarch64/aarch64.cc (aarch64_vector_costs::determine_suggested_unroll_factor): Take a loop_vec_info as argument. Restrict the unroll factor to values that divide the VF. (aarch64_vector_costs::finish_cost): Update call accordingly. gcc/testsuite/ PR tree-optimization/105254 * g++.dg/vect/pr105254.cc: New test.
next prev parent reply other threads:[~2022-04-13 16:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-13 6:34 [Bug tree-optimization/105254] New: " asolokha at gmx dot com 2022-04-13 8:00 ` [Bug tree-optimization/105254] " marxin at gcc dot gnu.org 2022-04-13 8:10 ` marxin at gcc dot gnu.org 2022-04-13 8:48 ` asolokha at gmx dot com 2022-04-13 12:53 ` rsandifo at gcc dot gnu.org 2022-04-13 16:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-13 17:02 ` rsandifo at gcc dot gnu.org 2022-06-15 10:13 ` cvs-commit at gcc dot gnu.org 2022-06-23 2:25 ` cvs-commit 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-105254-4-NmNhUBx4j2@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: 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).