From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>,
redi@gcc.gnu.org
Subject: Re: [PATCH libstdc++/66689] comp_ellint_3 and ellint_3 return garbage values
Date: Sat, 18 Nov 2017 16:49:00 -0000 [thread overview]
Message-ID: <fde24434-0c04-c369-8956-f9c4b0024bfb@verizon.net> (raw)
In-Reply-To: <20171117205429.GA31922@redhat.com>
On 11/17/2017 03:54 PM, Jonathan Wakely wrote:
>
> Hmm, you're probably right. I'd be tempted to though.
>
I had an idea. What about a macro _GLIBCXX_ELLINT_3_POS_NU or something
that:
1. would allow users to detect which convention is on by default.
2. They could set or unset to get the other convention.
It's bloody but it would work. it would prevent users from having to
test the compiler version and guess or check the value every time.
I feel that distros are likely to pick up gcc-7 soon and I'd like to do
*something*. This would be something of a transition path.
Ed
next prev parent reply other threads:[~2017-11-18 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 20:06 Ed Smith-Rowland
2017-11-17 20:54 ` Jonathan Wakely
2017-11-18 16:49 ` Ed Smith-Rowland [this message]
2017-11-20 16:39 ` Jonathan Wakely
2017-11-21 11:33 ` Florian Weimer
2017-11-21 13:35 ` Jonathan Wakely
2017-11-22 0:19 ` Joseph Myers
2017-11-20 16:02 David Edelsohn
2017-11-20 20:44 ` Christophe Lyon
2017-11-20 21:01 ` Jonathan Wakely
2017-11-20 21:07 ` Jonathan Wakely
2017-11-20 21:51 ` Jonathan Wakely
2017-12-05 18:36 ` David Edelsohn
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=fde24434-0c04-c369-8956-f9c4b0024bfb@verizon.net \
--to=3dw4rd@verizon.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=redi@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: 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).