public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/107240] [13 Regression] FAIL: gcc.dg/vect/vect-bitfield-write-2.c since r13-3219-g25413fdb2ac249
Date: Tue, 18 Oct 2022 05:56:14 +0000	[thread overview]
Message-ID: <bug-107240-4-IK1JGPNqit@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107240-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107240

--- Comment #8 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Kewen Lin from comment #7)
> Well, it does helps vect-bitfield-write-{2,3}.c, but it doesn't help
> vect-bitfield-write-{2,3,4}.c since they do require vector/vector shift

Oops, typo here, should be vect-bitfield-read-{2,3,4}.c.

  parent reply	other threads:[~2022-10-18  5:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 18:48 [Bug testsuite/107240] New: [13 regression] seurer at gcc dot gnu.org
2022-10-12 19:16 ` [Bug testsuite/107240] " bergner at gcc dot gnu.org
2022-10-13  6:49 ` [Bug testsuite/107240] [13 Regression] FAIL: gcc.dg/vect/vect-bitfield-write-2.c since r13-3219-g25413fdb2ac249 marxin at gcc dot gnu.org
2022-10-13 13:53 ` avieira at gcc dot gnu.org
2022-10-14  7:20 ` rguenth at gcc dot gnu.org
2022-10-14 16:44 ` segher at gcc dot gnu.org
2022-10-14 16:45 ` avieira at gcc dot gnu.org
2022-10-14 16:48 ` segher at gcc dot gnu.org
2022-10-17  4:04 ` linkw at gcc dot gnu.org
2022-10-17  6:21 ` linkw at gcc dot gnu.org
2022-10-18  5:56 ` linkw at gcc dot gnu.org [this message]
2022-10-18  8:06 ` rguenth at gcc dot gnu.org
2022-10-20  9:08 ` cvs-commit at gcc dot gnu.org
2022-10-28  3:31 ` cvs-commit at gcc dot gnu.org
2022-10-28  3:44 ` linkw 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-107240-4-IK1JGPNqit@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: link
Be 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).