-
Notifications
You must be signed in to change notification settings - Fork 558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ext/POSIX/t/math.t failure #17033
Comments
From rares.aioanei@gmail.comCreated by rares.aioanei@gmail.comSubject: ext/POSIX/t/math.t failure This is a bug report for perl from rares.aioanei@gmail.com, ----------------------------------------------------------------- # Failed test 'tanh(-1)' # Failed test 'tanh(1) == -tanh(-1)' Perl Info
|
From @jkeenanOn Mon, 03 Jun 2019 19:18:10 GMT, rares.aioanei@gmail.com wrote:
Are you in a position to run a test where you add the following option to Perl's ./Configure program? ##### That is, configure and build like this: ##### ... and then run: ##### I ask, because if the test in question PASSes when perl is configured with '-Duse64bitall', that would be consistent with some smoke test reports we have been receiving, e.g., http://perl5.test-smoke.org/report/88747 Unfortunately, while we have been receiving these smoke-test reports, we haven't been in position to fully diagnose this on Solaris. Thank you very much. -- |
The RT System itself - Status changed from 'new' to 'open' |
From @sisyphus
To the OP: Also (as a stab in the dark), on your first build, could you confirm that tanh(-1) and tanh(-1.0) are both returning the same incorrect value of 0.761594155955765. Cheers, |
From rares.aioanei@gmail.comOn Mon, 03 Jun 2019 18:16:09 -0700, sisyphus@cpan.org wrote:
Attached is the output of 'perl -V' as requested. 'make test' succeeds and both calls to tanh() return the same value, the one you predicted. Please let me know if there is anything else or if you need testing on Solaris in the future. |
From @sisyphusOn Fri, 07 Jun 2019 06:39:03 -0700, rares.aioanei@gmail.com wrote:
We can see from that 'perl -V' output that the "-Duse64bitall" argument puts the C compiler into 64 bit mode. Should we consider providing a fix/workaround for the 32 bit mode calculation ? Cheers, |
From rares.aioanei@gmail.comOn Fri, 07 Jun 2019 07:15:21 -0700, sisyphus@cpan.org wrote:
Just a side norte here....the perl compiled with '-Duse64bitall' returns the same values when calling tanh() as the 32-bit one does, although the math.t test fails only with the 32-bit one. |
From @jkeenanOn Fri, 07 Jun 2019 14:15:21 GMT, sisyphus@cpan.org wrote:
One possible approach: revise hints/solaris_2.sh. The string 'use64bitall' already occurs within that (and other) hints files. -- |
From rares.aioanei@gmail.comYes, they return the same value. And here's the output of perl -V : Summary of my perl5 (revision 5 version 30 subversion 0) configuration: Platform: Characteristics of this binary (from libperl): On Tue, Jun 4, 2019 at 4:16 AM sisyphus@cpan.org via RT
|
From @tonycozOn Mon, 03 Jun 2019 12:18:10 -0700, rares.aioanei@gmail.com wrote:
This looks like it's caused by: https://www.illumos.org/issues/11175 and my illumos-2d6125aab2 system passes these tests when built without -Duse64bitint. Tony |
From @jkeenanOn Thu, 01 Aug 2019 04:12:36 GMT, tonyc wrote:
Will we have to wait for a new release of Illumos in order to close this ticket? Thank you very much. |
From @tonycozOn Fri, 02 Aug 2019 18:43:48 -0700, jkeenan wrote:
The OP appears to be running a development release of OpenIndiana. 2019.04 has illumos at git commit a547acf91a[1], Sun Apr 28 18:59:18 2019 +0000. The OP's uname string indicates they have a later prerelease ffec1fd1b2, Thu May 9 17:19:27 2019 +0000. The release I downloaded, which includes the fix is dated Sat Jun 22 10:26:20 2019 +0300. I expect the OP could already update to fix the issue. Tony |
From @tonycozOn Sun, 04 Aug 2019 18:01:16 -0700, tonyc wrote:
Since this is fixed upstream, closing. Tony |
@tonycoz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#134171 (status was 'resolved')
Searchable as RT134171$
The text was updated successfully, but these errors were encountered: