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/dmf007)] Update ChangeLog.meissner Date: Wed, 1 Feb 2023 06:28:02 +0000 (GMT) [thread overview] Message-ID: <20230201062802.201E83858D38@sourceware.org> (raw) https://gcc.gnu.org/g:3d0eb0096c1513f0fdf6ea7bea8721255a21860d commit 3d0eb0096c1513f0fdf6ea7bea8721255a21860d Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Feb 1 01:27:58 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index c361afa4260..d7a41436152 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,13 @@ +==================== dmf007, patch #39 ==================== + +Fix dmr test. + +2023-02-01 Michael Meissner <meissner@linux.ibm.com> + +gcc/testsuite/ + + * gcc.target/powerpc/dm-double-test.s: Fix test to use dmsetdmrz. + ==================== dmf007, patch #38 ==================== Bump up precision size to 11 bits.
next reply other threads:[~2023-02-01 6:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 6:28 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-02-02 2:59 Michael Meissner 2023-02-01 17:35 Michael Meissner 2023-02-01 3:10 Michael Meissner 2023-01-28 7:14 Michael Meissner 2023-01-28 3:21 Michael Meissner 2023-01-23 21:19 Michael Meissner 2023-01-23 21:19 Michael Meissner 2023-01-23 21:18 Michael Meissner 2023-01-21 3:27 Michael Meissner 2023-01-20 22:22 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=20230201062802.201E83858D38@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).