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/work096)] Update ChangeLog.meissner. Date: Thu, 4 Aug 2022 22:50:56 +0000 (GMT) [thread overview] Message-ID: <20220804225056.754543858407@sourceware.org> (raw) https://gcc.gnu.org/g:ae29cffdc0948f40663ed09d45c27fe8344824ba commit ae29cffdc0948f40663ed09d45c27fe8344824ba Author: Michael Meissner <meissner@linux.ibm.com> Date: Thu Aug 4 18:50:39 2022 -0400 Update ChangeLog.meissner. 2022-08-04 Michael Meissner <meissner@linux.ibm.com> gcc/ * ChangeLog.meissner: Update. Diff: --- gcc/ChangeLog.meissner | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/gcc/ChangeLog.meissner b/gcc/ChangeLog.meissner index 5cdeae3a44b..9a3bf0390e6 100644 --- a/gcc/ChangeLog.meissner +++ b/gcc/ChangeLog.meissner @@ -1,3 +1,28 @@ +==================== work096, patch 12. + +Make 'w' the __ibm128 suffix. + +In writing code with __ibm128 support, it would be nice if we supported a suffix +that marked __ibm128 constants. The preprocessor lexer supports using either +'q'/'Q' or 'w'/'W' as machine dependent suffixes. The 'q'/'Q' suffix was +already taken for __float128 constants, so I added 'w' or 'W' as the suffix for +the __ibm128 constant. + +I went to the file doc/extend.texi to document using a 'w' or 'W' suffix, but it +appears that we already had documented using 'w'/'W' for __ibm128. This code +adds this support to the GCC compiler. + +2022-08-04 Michael Meissner <meissner@linux.ibm.com> + +gcc/ + + * config/rs6000/rs6000.cc (rs6000_c_mode_for_suffix): Add support for + using 'w' or 'W' as the __ibm128 bit constant. + +gcc/testsuite/ + + * gcc.target/powerpc/ibm128-suffix.c: New test. + ==================== work096, patch 11. Mangle __ibm128 to u8__ibm128.
next reply other threads:[~2022-08-04 22:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-04 22:50 Michael Meissner [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-08-03 15:36 Michael Meissner 2022-08-03 15:14 Michael Meissner 2022-08-02 21:34 Michael Meissner 2022-08-02 19:35 Michael Meissner 2022-08-02 18:50 Michael Meissner 2022-08-02 18:00 Michael Meissner 2022-08-02 4:26 Michael Meissner 2022-08-02 0:38 Michael Meissner 2022-08-01 22:12 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=20220804225056.754543858407@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).