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
test suite failure on powerpc with -Duselongdouble #10362
Comments
From @ntyniThis is a bug report for perl from Niko Tyni <ntyni@debian.org>, I'm seeing 5.12.0 test failures on the Debian powerpc architecture Test Summary Report op/inc.t (Wstat: 65280 Tests: 34 Failed: 0) At least op/pack.t fails on 5.10.1 too, so this is not a 5.12 regression. I assume the 128-bit long doubles on this platform are actually a sum of If this something that can not be supported, perhaps Configure should (This is also http://bugs.debian.org/578295 ) [1] http://en.wikipedia.org/wiki/Long_double Flags: Site configuration information for perl 5.12.0: Configured by Debian Project at Sun May 2 12:18:53 UTC 2010. Summary of my perl5 (revision 5 version 12 subversion 0) configuration: Locally applied patches: @INC for perl 5.12.0: Environment for perl 5.12.0: |
From @nwc10On Mon, May 03, 2010 at 01:30:34AM -0700, Niko Tyni wrote:
That seems a reasonable assumption, given that sparc64 Debian with 16 byte
That seems reasonable. Not sure how to do it.
Nicholas Clark |
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgNiko Tyni wrote:
A double-double format *can* be well-behaved, if its two halves are Can someone offer me an account on one of these PowerPC Linux systems -zefram |
From @sisyphus-----Original Message-----
I have such a system - though I'm unable to provide you with access to it. For some additional info on the M::BI failures, see: I've been consistently seeing those failures, right through to the present Until recently, those have been the only tests that were failing. (I think With perl-5.27.6, I get: ####################################### # Testing for subsecond file timestamps (mtime) in I have neither investigated nor filed a report for those utime.t failures. Cheers, |
Migrated from rt.perl.org#74864 (status was 'open')
Searchable as RT74864$
The text was updated successfully, but these errors were encountered: