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/111866] [14 regression] ICE when compiling gcc.target/powerpc/p9-vec-length-full-7.c Date: Fri, 20 Oct 2023 14:00:53 +0000 [thread overview] Message-ID: <bug-111866-4-3if4fhYqOx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111866-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111866 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>: https://gcc.gnu.org/g:eb15fad3190a8b33e3e451b964ff1ecf08bbb113 commit r14-4792-geb15fad3190a8b33e3e451b964ff1ecf08bbb113 Author: Tamar Christina <tamar.christina@arm.com> Date: Fri Oct 20 14:58:39 2023 +0100 middle-end: don't pass loop_vinfo to vect_set_loop_condition during prolog peeling During the refactoring I had passed loop_vinfo on to vect_set_loop_condition during prolog peeling. This parameter is unused in most cases except for in vect_set_loop_condition_partial_vectors where it's behaviour depends on whether loop_vinfo is NULL or not. Apparently this code expect it to be NULL and it reads the structures from a different location. This fixes the failing testcase which was not using the lens values determined earlier in vectorizable_store because it was looking it up in the given loop_vinfo instead. gcc/ChangeLog: PR tree-optimization/111866 * tree-vect-loop-manip.cc (vect_do_peeling): Pass null as vinfo to vect_set_loop_condition during prolog peeling.
next prev parent reply other threads:[~2023-10-20 14:00 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-18 15:49 [Bug middle-end/111866] New: [14 regression] ICE when compiling seurer at gcc dot gnu.org 2023-10-18 16:06 ` [Bug middle-end/111866] [14 regression] ICE when compiling gcc.target/powerpc/p9-vec-length-full-7.c tnfchris at gcc dot gnu.org 2023-10-18 16:07 ` [Bug tree-optimization/111866] " tnfchris at gcc dot gnu.org 2023-10-18 18:57 ` pinskia at gcc dot gnu.org 2023-10-19 11:07 ` tnfchris at gcc dot gnu.org 2023-10-20 10:58 ` tnfchris at gcc dot gnu.org 2023-10-20 14:00 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-20 14:02 ` tnfchris 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-111866-4-3if4fhYqOx@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).