From: Christophe Lyon <christophe.lyon@linaro.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Ed Smith-Rowland <3dw4rd@verizon.net>,
"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: Mon, 20 Nov 2017 20:44:00 -0000 [thread overview]
Message-ID: <CAKdteOYtMKdVJPCuCQLW2eB+X8P_WtiHfvXN9oryt31ewOeR8Q@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnymGWZr2Cnei_GmGRNc24L=AkYvVAiSNAe16_xBtQQ_ZbQ@mail.gmail.com>
On 20 November 2017 at 17:02, David Edelsohn <dje.gcc@gmail.com> wrote:
> This patch has introduced new regressions on at least PowerPC and AArch64.
>
> FAIL: ext/special_functions/hyperg/check_value.cc execution test
> FAIL: tr1/5_numerical_facilities/special_functions/17_hyperg/check_value.cc
> execution test
>
> Thanks, David
On AArch64 and ARM, I have also noticed
FAIL: special_functions/18_riemann_zeta/check_value.cc (test for excess errors)
UNRESOLVED: special_functions/18_riemann_zeta/check_value.cc
compilation failed to produce executable
because:
/libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc:
In function 'void test(const testcase_riemann_zeta<Ret> (&)[Num],
Ret)':
/libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc:292:
error: 'riemann_zeta' is not a member of 'std'
/libstdc++-v3/testsuite/special_functions/18_riemann_zeta/check_value.cc:292:
note: suggested alternative: 'remainder'
compiler exited with status 1
next prev parent reply other threads:[~2017-11-20 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 16:02 David Edelsohn
2017-11-20 20:44 ` Christophe Lyon [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-11-17 20:06 Ed Smith-Rowland
2017-11-17 20:54 ` Jonathan Wakely
2017-11-18 16:49 ` Ed Smith-Rowland
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
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=CAKdteOYtMKdVJPCuCQLW2eB+X8P_WtiHfvXN9oryt31ewOeR8Q@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=3dw4rd@verizon.net \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).