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 target/105122] [12 Regression] Testsuite failures since r12-7931 on i686-linux Date: Wed, 06 Apr 2022 06:15:01 +0000 [thread overview] Message-ID: <bug-105122-4-wjo6r5hnCw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105122-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105122 --- Comment #4 from CVS 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:e2a818641ba5d07ebe2c241906896c4886910d18 commit r12-8011-ge2a818641ba5d07ebe2c241906896c4886910d18 Author: Richard Biener <rguenther@suse.de> Date: Mon Apr 4 08:41:59 2022 +0200 testsuite/105122 - adjust testcases after memcpy folding changes After r12-7931 we again honor MOVE_MAX when folding memcpy to a load/store pair. On i?86-*-* without SSE this now exposes the change done in r12-2666-g29f0e955c97da0 which adjusts MOVE_MAX from 16 to 4 on those targets. This makes adjusting testcases necessary that assume that we transform memcpy to load/store pairs on GIMPLE for sizes larger or equal to 8. 2022-04-04 Richard Biener <rguenther@suse.de> PR testsuite/105122 * gcc.dg/memcpy-6.c: Adjust. * gcc.dg/strlenopt-73.c: Likewise. * gcc.dg/strlenopt-80.c: Likewise.
next prev parent reply other threads:[~2022-04-06 6:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-01 10:29 [Bug target/105122] New: " jakub at gcc dot gnu.org 2022-04-01 10:29 ` [Bug target/105122] " jakub at gcc dot gnu.org 2022-04-01 12:08 ` rguenth at gcc dot gnu.org 2022-04-01 12:41 ` rguenth at gcc dot gnu.org 2022-04-04 6:41 ` rguenth at gcc dot gnu.org 2022-04-06 6:15 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-06 6:15 ` rguenth 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-105122-4-wjo6r5hnCw@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).