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 17:35:31 +0000 (GMT) [thread overview] Message-ID: <20230201173531.E96063858D33@sourceware.org> (raw) https://gcc.gnu.org/g:6569abbe7968409a5433508c8d618d90e9013f9e commit 6569abbe7968409a5433508c8d618d90e9013f9e Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Feb 1 12:35:28 2023 -0500 Update ChangeLog.meissner Diff: --- gcc/ChangeLog.meissner | 34 +++++++++++++++++++--------------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index d7a41436152..be0f215b9a5 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,16 +1,6 @@ -==================== dmf007, patch #39 ==================== - -Fix dmr test. +==================== dmf007, patch #40 ==================== -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. +Bump up precision size to 16 bits. The new __dmr type that is being added as a possible future PowerPC instruction set bumps into a structure field size issue. The size of the __dmr type is 1024 bits. @@ -28,13 +18,27 @@ before the two shifts, while the PowerPC always returns 0. In the ccp pass, the original input is -1, and so it worked. When I did the runs on the PowerPC, the result was 0, which ultimately led to the failure. -2023-01-31 Michael Meissner <meissner@linux.ibm.com> +2023-02-01 Richard Biener <rguenther@suse.de> + Michael Meissner <meissner@linux.ibm.com> gcc/ + PR middle-end/108623 * hwint.h (sext_hwi): Add assertion against precision 0. - * tree-core.h (tree_type_common): Bump up precision field by 1 bit, and - reduce contains_placeholder_bits to 1 bit. + * tree-core.h (tree_type_common): Bump up precision field to 16 bits. + Align bit fields > 1 bit to at least an 8-bit boundary. + +==================== 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 was reverted ==================== ==================== dmf007, patch #37 ====================
next reply other threads:[~2023-02-01 17:35 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-01 17:35 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-02-02 2:59 Michael Meissner 2023-02-01 6:28 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=20230201173531.E96063858D33@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).