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/113026] Bogus -Wstringop-overflow warning on simple memcpy type loop Date: Mon, 08 Jan 2024 13:52:35 +0000 [thread overview] Message-ID: <bug-113026-4-CSLN5W9QSL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113026-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113026 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:b3cc5a1efead520bc977b4ba51f1328d01b3e516 commit r14-7003-gb3cc5a1efead520bc977b4ba51f1328d01b3e516 Author: Richard Biener <rguenther@suse.de> Date: Fri Dec 15 10:32:29 2023 +0100 tree-optimization/113026 - avoid vector epilog in more cases The following avoids creating a niter peeling epilog more consistently, matching what peeling later uses for the skip_vector condition, in particular when versioning is required which then also ensures the vector loop is entered unless the epilog is vectorized. This should ideally match LOOP_VINFO_VERSIONING_THRESHOLD which is only computed later, some refactoring could make that better matching. The patch also makes sure to adjust the upper bound of the epilogues when we do not have a skip edge around the vector loop. PR tree-optimization/113026 * tree-vect-loop.cc (vect_need_peeling_or_partial_vectors_p): Avoid an epilog in more cases. * tree-vect-loop-manip.cc (vect_do_peeling): Adjust the epilogues niter upper bounds and estimates. * gcc.dg/torture/pr113026-1.c: New testcase. * gcc.dg/torture/pr113026-2.c: Likewise.
next prev parent reply other threads:[~2024-01-08 13:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-14 21:42 [Bug tree-optimization/113026] New: " bergner at gcc dot gnu.org 2023-12-14 21:47 ` [Bug tree-optimization/113026] " pinskia at gcc dot gnu.org 2023-12-15 9:24 ` rguenth at gcc dot gnu.org 2023-12-15 10:20 ` rguenth at gcc dot gnu.org 2023-12-15 13:10 ` avieira at gcc dot gnu.org 2023-12-18 7:14 ` rguenther at suse dot de 2024-01-08 13:52 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-08 13:54 ` rguenth at gcc dot gnu.org 2024-01-09 12:37 ` cvs-commit at gcc dot gnu.org 2024-01-20 18:38 ` pinskia 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-113026-4-CSLN5W9QSL@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).