George Greer 'wrote':
Compiler messages(MSWin32):
..\pp_sys.c(4610) : error C2063: '_isnan' : not a function
perl.h has this:
#ifdef WIN32
# ifndef Perl_isnan
#define Perl_isnan(x) _isnan(x)
# endif
so it seems Perl_isnan will always be defined on Windows. But in var-
ious places we
George Greer wrote:
Failures: (common-args) -Accflags=-fsanitize=address
-Werror=declaration-after-statement -Aldflags=-fsanitize=address -Dcc=clang
[default]
[default] -DDEBUGGING
../t/op/closure.t...FAILED
139-140, 151-152, 253-254
Jarkko Hietaniemi wrote:
On Thursday-201409-25, 9:23, Steve Hay wrote:
Now bisected to 5564cd7fcb7851d713d898c22f57e6562a43a53c.
So... is this still broken? Threaded builds are still happy, which is
what 5564cd7fcb7851d713d898c22f57e6562a43a53c was fixing.
The bad code was added in
Jarkko Hietaniemi wrote:
grep -n 'bool .* = .*OK' *.c|grep -v cBOOL
finds some potential trouble places.
SvUOK is defined in terms of ==. Anything with on the rhs is fine.
So those are false positives.
Jarkko Hietaniemi wrote:
On Tuesday-201409-02, 1:20, Father Chrysostomos wrote:
Jarkko Hietaniemi wrote:
If you need more information I can do a build and run the test.
Yes, that would be helpful.
Oh, sorry, that was cut-and-paste from George. I have no access to his
Win32, I just
George Greer 'wrote':
[default] -Duseithreads
[default] -DDEBUGGING -Duseithreads
../t/op/taint.t.FAILED
800
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the
Jarkko Hietaniemi wrote:
It's inconvenient for me to go digging through the logs. Could some-
one with Windows run './perl -Ilib t/op/taint.' and post the output?
The failures I'm getting from a reasonably fresh (last night) build are:
# Failed
Jarkko Hietaniemi wrote:
Log says:
# Failed test 800 - tainted constant as logop condition should not
prevent use at op/taint.t line 2326
# got undef
# expected 122669\n
Thank you. You saved me some time.
If you need more information I can do a build and run the test.
Yes, that
George Greer âwroteâ:
[default]
[default] -DDEBUGGING
[default] -Duseithreads
[default] -DDEBUGGING -Duseithreads
../t/op/tie.t...FAILED
79
The logs say:
EXPECTED:
c3
bf
--
c3
bf
GOT:
Is it crashing? If so, will a backtrace be
Steve Hay wrote:
Yes, the following program crashes:
use Tie::Array;
tie @_, Tie::StdArray;
@_ = \xff;
{sub { goto utf8::encode }};
Thank you!
But argh!!! I even used cBOOL at first, then when I refactored
slightly I accidentally got rid of it.
George Greer âwroteâ:
../t/re/pat.t...FAILED
228-231
../t/op/taint.t.FAILED
592
OK, so which of my commits caused these? They make no sense to me.
Steve Hay wrote:
t/re/pat.t, t/re/pat_thr.t, t/op/taint.t and
dist/threads-shared/t/clone.t all fail (in a threaded build) at
c9f1f591ba751b24222b22f1f3a6799db0ab0d1b (Read-only COWs), the first
of your three merge commits.
Thank you. Can you tell which commit in the branch caused it?
What
Steve Hay wrote:
The tests fail in commit 3805b5fb04f8819edfb6bd5256d5eefd7b23e730
Thank you! clang is being âhelpfulâ and preventing me from spotting
errors like this. Does the sprout/taint-failure branch make the fail-
ures go away?
Does that IPC-Cmd failure have anything to do with this?
On Jul 21, 2011, at 10:52 PM, George Greer wrote:
Smoke logs available at http://m-l.org/~perl/smoke/perl/
Automated smoke report for 5.15.1 patch
56b53eb647b1791ce531707156c5ecbb2d5a2ddf v5.15.1-24-g56b53eb
perl-win2k: Intel(R)
14 matches
Mail list logo
