public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Meissner <meissner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/meissner/heads/work121)] Revert patches Date: Fri, 12 May 2023 23:09:07 +0000 (GMT) [thread overview] Message-ID: <20230512230907.C22473857031@sourceware.org> (raw) https://gcc.gnu.org/g:79e868a33f8315afdc97590fbf5317fac09a612a commit 79e868a33f8315afdc97590fbf5317fac09a612a Author: Michael Meissner <meissner@linux.ibm.com> Date: Fri May 12 19:09:04 2023 -0400 Revert patches Diff: --- gcc/testsuite/gcc.target/powerpc/vec-extract-mem-float-2.c | 0 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/gcc/testsuite/gcc.target/powerpc/vec-extract-mem-float-2.c b/gcc/testsuite/gcc.target/powerpc/vec-extract-mem-float-2.c deleted file mode 100644 index e69de29bb2d..00000000000
next reply other threads:[~2023-05-12 23:09 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-12 23:09 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-06-03 4:03 Michael Meissner 2023-06-02 14:45 Michael Meissner 2023-05-18 4:58 Michael Meissner 2023-05-15 20:42 Michael Meissner 2023-05-12 22:54 Michael Meissner 2023-05-12 21:58 Michael Meissner 2023-05-12 21:33 Michael Meissner 2023-05-12 16:51 Michael Meissner 2023-05-12 16:51 Michael Meissner 2023-05-12 16:51 Michael Meissner 2023-05-12 16:50 Michael Meissner 2023-05-12 16:50 Michael Meissner 2023-05-12 16:50 Michael Meissner 2023-05-12 16:50 Michael Meissner 2023-05-10 15:08 Michael Meissner 2023-05-09 20:33 Michael Meissner 2023-05-09 16:28 Michael Meissner 2023-05-08 23:26 Michael Meissner 2023-05-08 23:21 Michael Meissner 2023-05-08 23:20 Michael Meissner 2023-05-08 22:17 Michael Meissner
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=20230512230907.C22473857031@sourceware.org \ --to=meissner@gcc.gnu.org \ --cc=gcc-cvs@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).