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/dmf003)] Update ChangeLog.meissner. Date: Wed, 9 Nov 2022 05:02:17 +0000 (GMT) [thread overview] Message-ID: <20221109050217.07EC93858C62@sourceware.org> (raw) https://gcc.gnu.org/g:8a27ebb2c6419a371f366d77d0ed6c7c126c8b1c commit 8a27ebb2c6419a371f366d77d0ed6c7c126c8b1c Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Nov 9 00:01:53 2022 -0500 Update ChangeLog.meissner. 2022-11-09 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 64296fff8aa..72065f8fec4 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,14 @@ +==================== Dmf003 branch, patch #17. + +Turn off CCP when testing __dmr. + +2022-11-09 Michael Meissner <meissner@linux.ibm.com> + +gcc/testsuite/ + + * gcc.target/powerpc/dm-1024bit.c: Add -fno-tree-ccp until CCP can + handle OPAQUE types. + ==================== Dmf003 branch, patch #16. Fix spacing.
next reply other threads:[~2022-11-09 5:02 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-09 5:02 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-11-09 5:34 Michael Meissner 2022-11-08 16:04 Michael Meissner 2022-11-05 4:23 Michael Meissner 2022-11-05 3:27 Michael Meissner 2022-11-05 3:01 Michael Meissner 2022-11-04 23:24 Michael Meissner 2022-11-04 22:56 Michael Meissner 2022-11-04 21:13 Michael Meissner 2022-11-04 17:09 Michael Meissner 2022-11-04 7:14 Michael Meissner 2022-11-04 6:38 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=20221109050217.07EC93858C62@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).