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/work101)] Update ChangeLog.meissner. Date: Thu, 3 Nov 2022 02:29:53 +0000 (GMT) [thread overview] Message-ID: <20221103022954.0683F3858C78@sourceware.org> (raw) https://gcc.gnu.org/g:e12a3ea85034ff963c51f3d46d0175aa3fc248ed commit e12a3ea85034ff963c51f3d46d0175aa3fc248ed Author: Michael Meissner <meissner@linux.ibm.com> Date: Wed Nov 2 22:29:37 2022 -0400 Update ChangeLog.meissner. 2022-11-02 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- libgcc/ChangeLog.meissner | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/libgcc/ChangeLog.meissner b/libgcc/ChangeLog.meissner index a0706e92964..a4634b6ad7b 100644 --- a/libgcc/ChangeLog.meissner +++ b/libgcc/ChangeLog.meissner @@ -1,3 +1,18 @@ +==================== Work101, patch #4 + +Patch libgcc to always use _Float128 and _Complex _Float128 on PowerPC. + +2022-11-02 Michael Meissner <meissner@linux.ibm.com> + + * config/rs6000/quad-float128.h (TF): Delete definition. + (TFtype): Define to be _Float128. + (TCtype): Change to be _Complex _Float128. + * libgcc2.h (TFtype): Allow MD code to override definition. + (TCtype): Likewise. + * soft-fp/quad.h (TFtype): Likewise. + +==================== Work101, initial branch. + 2022-10-06 Michael Meissner <meissner@linux.ibm.com> Clone branch
next reply other threads:[~2022-11-03 2:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-03 2:29 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-10-29 3:18 Michael Meissner 2022-10-28 2:22 Michael Meissner 2022-10-27 20:59 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=20221103022954.0683F3858C78@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).