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 target/108807] [11/12 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after r11-6857-gb29225597584b6 on power 9 BE
Date: Sat, 15 Apr 2023 09:55:55 +0000 [thread overview]
Message-ID: <bug-108807-4-I8hujH8JRR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108807-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108807
--- Comment #6 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #5)
> Kewen, is this BZ fixed on the trunk? If so we should update the title by
> dropping the "/13" so that's not flagged as a gcc-13 regression.
Yes, thanks for reminding and tips! I didn't know this rule before, I had a
related question that I'm going to backport the commit to gcc-11/gcc-12 soon,
once it's done excepting for marking the status to resolved, should I also drop
the remaining "[11/12 regression]"? Or for a bug in resolved status, not
dropping it would be fine?
next prev parent reply other threads:[~2023-04-15 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 19:16 [Bug target/108807] New: [11 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after b29225597584b697762585e0b707b7cb4b427650 " seurer at gcc dot gnu.org
2023-02-16 7:41 ` [Bug target/108807] " linkw at gcc dot gnu.org
2023-02-17 4:09 ` [Bug target/108807] [11/12/13 regression] gcc.target/powerpc/vsx-builtin-10d.c fails after r11-6857-gb29225597584b6 " linkw at gcc dot gnu.org
2023-02-17 5:26 ` linkw at gcc dot gnu.org
2023-03-15 10:02 ` rguenth at gcc dot gnu.org
2023-04-04 5:13 ` cvs-commit at gcc dot gnu.org
2023-04-14 15:33 ` law at gcc dot gnu.org
2023-04-15 9:55 ` linkw at gcc dot gnu.org [this message]
2023-04-15 13:19 ` [Bug target/108807] [11/12 " law at gcc dot gnu.org
2023-04-17 9:06 ` cvs-commit at gcc dot gnu.org
2023-04-17 9:08 ` cvs-commit at gcc dot gnu.org
2023-04-17 9:10 ` 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-108807-4-I8hujH8JRR@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).