REIX Tony added the comment:
OK.
However, compiling ONLY the file Objects/longobject.c with -qalias=noansi did
fix the issue on AIX. That could be the same on Linux.
I haven't tried to use Py_SIZE() in all places where it should be used. Now
trying to figure out why GCC behaves worst
REIX Tony added the comment:
With XLC v13 -O2, using -qalias=noansi for building Objects/longobject.o only
and not for all the other .o files did fix the 10 more failed tests I see with
-O2 compared to -O0 (7-8 failed tests).
So, ANSI-aliasing in Objects/longobject.c is the issue.
About
REIX Tony added the comment:
Thanks a lot Stefan, that should completely explain my issues.
-fno-strict-aliasing -fwrapv for gcc
So, that means that you would get better performance if you applied on Python
v2.7 what Python v3.5 did about Py_SIZE(x) .
However, there are probably other places
REIX Tony added the comment:
Hi Raymond
I've got several email exchanges with the IBM XLC expert. From his own study of
my issue, his conclusion is that this kind of Python v2 coding is not
ANSI-aliasing safe. It seems that there is a standard that requires C code to
NOT do some kin
New submission from REIX Tony:
I'm porting Python 2.7.* on AIX.
I am now using a version 13.1.3.2 of XLC.
I was previously using version 12.1.0.14 .
It appears that this new compiler shows a potential issue in Python v2 code.
This issue seems to appear when -O2 is used.
I was porting P
REIX Tony added the comment:
I'm now working about the port of Python 3.4.3 on AIX.
So, I'm interesting with issues dealing with AIX.
I'm now building a view of the issues on AIX 6.1 .
--
nosy: +trex58
___
Python tracker
<http
REIX Tony added the comment:
Fresh openssl versions are now available for AIX: 1.0.1p and 1.0.2d .
See: http://www.bullfreeware.com/search.php?package=openssl
--
nosy: +trex58
___
Python tracker
<http://bugs.python.org/issue24
REIX Tony added the comment:
Yes. I'm on my own for AIX debugging. I'm afraid too.
;)
OK. What I need is build more skills about how to get into deep details when
things run badly. Lot of fun. ;)
Thx
--
___
Python tracker
<http://bu
REIX Tony added the comment:
About test_io, when running it alone by:
./python ./Lib/test/test_io.py > /tmp/test_io.res
I got NO error !
Done 2 times on each of my 2 AIX machines.
Hu Why these tests do block in the middle ?
--
___
Pyt
REIX Tony added the comment:
I got strange things:
Tests blocked in:
[300/400/22] test_signal
and:
# ps -edf | grep python
root 7405612 12320954 0 14:52:04 pts/2 0:00 ./python -m -c -l -x
test_io
root 7929900 34209932 0 14:52:04 pts/2 0:00 ./python -m -c -l -x
test_io
REIX Tony added the comment:
Hum
I'm now building Python 2.7.10 RPMs on AIX.
The .spec file works fine.
However, when adding make test in the .spec file, I've got the tests blocked in
test_io. The same with 2.7.6 .
Going into the directory and trying "make quicktest"
REIX Tony added the comment:
Thnaks for the information.
I'm surprised that:
$ make test > Go.res3 2>&1 &
makes issues that do not appear with:
$ nohup make test > Go.res3 2>&1 &
Anyway, we know the root cause now, and there is a work-around.
So, closing th
REIX Tony added the comment:
run on Ubuntu/i586 :
$ make test > Go.res3 2>&1 &
$ tail -f Go.res
[164/390] test_cgi
Silent !
^C
[1]+ Stoppedmake test > Go.res3 2>&1
reixt@b017569-ux:~/FromOldPC/FromOldPC/Projets/ToolBox/PYTHON-3/Python-
New submission from REIX Tony:
I'm now porting Python (2.7.10 and 3.4.3) on AIX.
Before that, I wanted to build and test on reference machines in order to see
what is expected during building and testing.
However, on Ubuntu/i586 and Ubuntu/x86_64, I face hangs and errors during test
pha
14 matches
Mail list logo
