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 testsuite/108898] [13 Regression] Test introduced by r13-6278-g3da77f217c8b2089ecba3eb201e727c3fcdcd19d failed on i386 Date: Tue, 21 Mar 2023 12:44:13 +0000 [thread overview] Message-ID: <bug-108898-4-xwzPuWDvnD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108898-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108898 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:49a8bce43cdc1d1b48efa5eeb2a4097cfca1dc22 commit r13-6785-g49a8bce43cdc1d1b48efa5eeb2a4097cfca1dc22 Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Mar 21 13:42:51 2023 +0100 testsuite: Remove obsolete comments [PR108898] On Tue, Mar 21, 2023 at 12:35:19PM +0000, Andrew Stubbs wrote: > > /* Ensure the the in-branch simd clones are used on targets that support them. > > Some targets use another call for the epilogue loops. */ > > -/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" { target { ! aarch64*-*-* } } } } */ > > -/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 3 "vect" { target aarch64*-*-* } } } */ > > +/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" } } */ > > I suppose those comments are now obsolete. Oops, fixed thusly. 2023-03-21 Jakub Jelinek <jakub@redhat.com> PR testsuite/108898 * gcc.dg/vect/vect-simd-clone-16.c: Remove parts of comment mentioning epilogue loops. * gcc.dg/vect/vect-simd-clone-17.c: Likewise. * gcc.dg/vect/vect-simd-clone-18.c: Likewise.
prev parent reply other threads:[~2023-03-21 12:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-23 6:28 [Bug testsuite/108898] New: " haochen.jiang at intel dot com 2023-02-23 8:47 ` [Bug testsuite/108898] " rguenth at gcc dot gnu.org 2023-02-23 9:21 ` ams at gcc dot gnu.org 2023-02-24 1:30 ` haochen.jiang at intel dot com 2023-03-15 9:57 ` rguenth at gcc dot gnu.org 2023-03-15 10:43 ` ams at gcc dot gnu.org 2023-03-21 12:29 ` cvs-commit at gcc dot gnu.org 2023-03-21 12:31 ` jakub at gcc dot gnu.org 2023-03-21 12:44 ` cvs-commit at gcc dot gnu.org [this message]
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-108898-4-xwzPuWDvnD@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).