From: Marek Polacek <polacek@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: Implement excess precision support for C++ [PR107097, PR323]
Date: Wed, 12 Oct 2022 14:17:33 -0400 [thread overview]
Message-ID: <Y0cEvegLEGQwZpOk@redhat.com> (raw)
In-Reply-To: <Y0VwowKL1r/QXhLo@tucnak>
On Tue, Oct 11, 2022 at 03:33:23PM +0200, Jakub Jelinek via Gcc-patches wrote:
> Hi!
>
> The following patch implements excess precision support for C++.
> Like for C, it uses EXCESS_PRECISION_EXPR tree to say that its operand
> is evaluated in excess precision and what the semantic type of the
> expression is.
One trivial thing: c-common.def says "An EXCESS_PRECISION_EXPR, currently
only used for C and Objective C, ..." which will no longer be accurate with
the patch.
Marek
prev parent reply other threads:[~2022-10-12 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 13:33 Jakub Jelinek
2022-10-12 18:08 ` Jason Merrill
2022-10-13 16:40 ` [PATCH] c++, v2: " Jakub Jelinek
2022-10-13 19:28 ` Jason Merrill
2022-10-12 18:17 ` Marek Polacek [this message]
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=Y0cEvegLEGQwZpOk@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
/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: link
Be 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).