00:05
fryguybob has quit [Ping timeout: 276 seconds]
00:05
fryguybob has joined #pypy
00:08
commandoline has quit [Remote host closed the connection]
00:08
commandoline has joined #pypy
00:17
jcea has quit [Remote host closed the connection]
00:26
jcea has joined #pypy
00:44
wleslie has joined #pypy
00:46
adamholmberg has joined #pypy
00:48
adamholmberg has quit [Remote host closed the connection]
00:55
adamholmberg has joined #pypy
00:55
jvesely has joined #pypy
01:05
adamholmberg has quit [Remote host closed the connection]
01:11
lritter has quit [Ping timeout: 265 seconds]
01:18
adamholmberg has joined #pypy
01:31
adamholmberg has quit [Remote host closed the connection]
02:56
jcea has quit [Quit: jcea]
05:08
junna has joined #pypy
05:13
junna has quit [Ping timeout: 240 seconds]
06:00
dmalcolm_ has joined #pypy
06:02
dmalcolm has quit [Ping timeout: 265 seconds]
06:16
<
mattip >
The x64 docker buildslave uses gcc 8.3. rpython asmgcroot tests are failing
06:16
<
mattip >
I think the problem is in assembler like this
06:17
<
mattip >
with .LHOT and .LCOLD labels
06:19
<
mattip >
I compared the *.s file to gcc 7.4, that was the biggest change
06:20
<
mattip >
and that label appears in the iterline failure in rpython/translator/c/gcc/trackgcroot.py:find_functions
06:46
<
mattip >
definitely gcc-8 related, when I run the test on Ubuntu 18.04 with "CC=gcc-8" it fails
07:12
<
mattip >
another option is to remove trackgcroot
07:14
<
wleslie >
could build with the shadowstack until we can update asmgcroot?
07:15
<
wleslie >
or replace it with something maintainable (like something DWARF based)
07:16
<
mattip >
this is only in tests. We don't use this in pypy
07:17
<
mattip >
well, we don't use it
*anymore*
07:17
<
wleslie >
what's the current rootfinder?
07:21
<
mattip >
maybe now is the time :)
07:27
<
wleslie >
I wholeheartedly approve. Which is a first for me on removal of code.
07:38
_whitelogger has joined #pypy
08:33
junna has joined #pypy
08:40
<
arigato >
mattip: yes, I agree to kill all related code if it starts failing tests
08:41
<
kenaan >
mattip pypy.org[extradoc] 957dc5e9e470 /source/download.txt: add pypy3.6 7.3.0rc1 hashes
08:41
<
mattip >
7.3.0rc1 release candidates are up
08:42
<
mattip >
antocuni was having problems with curses, I hope they have gone away now with ncurses6
08:42
<
arigato >
mattip: I can kill asmgcroot-related codes myself today
08:43
<
mattip >
there is scattered mentions in documentation and configuration too
08:53
tsaka__ has quit [Quit: Konversation terminated!]
08:54
tsaka__ has joined #pypy
09:05
<
cfbolz >
mattip: I had discussed it with armin, we should kill it
09:05
<
cfbolz >
ah, sorry, didn't read far enough :-)
09:18
<
tos9 >
(FWIW, GH Actions has PyPy{2,3} latest as of yesterday hooray)
09:21
<
tos9 >
cfbolz: also hello :)
09:22
<
cfbolz >
pretty good, new house and new baby :-)
09:22
tsaka__ has quit [Read error: Connection reset by peer]
09:23
<
tos9 >
congrats! figured it was about that time
09:24
<
tos9 >
all good here, in the EU for the next few weeks and not working, so those are both good things
09:25
<
cfbolz >
nice! whereabouts?
09:25
<
tos9 >
I'm in Portugal at the moment but we're probably going to drive to spain in the next few days
09:25
<
tos9 >
yeah pretty nice here, 16 and reasonably sunny is not bad for this time of year...
09:26
<
cfbolz >
beach weather by german standards :-P
09:54
junna has quit [Ping timeout: 240 seconds]
10:03
* arigato
is in 1 meter of snow
10:05
<
kenaan >
arigo kill-asmgcc b23b24b53574 /: in-progress: remove asmgcc completely (modern versions of gcc show test failures)
10:14
tsaka__ has joined #pypy
10:34
jvesely has quit [Quit: jvesely]
10:39
lritter has joined #pypy
11:32
senyai has quit [Quit: Leaving]
12:29
marky1991 has joined #pypy
12:29
marky1991 has quit [Remote host closed the connection]
12:30
marky1991 has joined #pypy
12:59
tsaka__ has quit [Ping timeout: 240 seconds]
13:26
<
mattip >
arigato: the rpython tests are now run separately ^^^
13:28
marky1991 has quit [Ping timeout: 268 seconds]
13:34
junna has joined #pypy
13:44
CountryNerd has joined #pypy
13:55
tsaka__ has joined #pypy
14:02
tsaka_ has joined #pypy
14:02
tsaka__ has quit [Ping timeout: 246 seconds]
14:28
<
arigato >
mattip: ah right, thanks
14:32
<
kenaan >
arigo kill-asmgcc 04030975247c /pypy/doc/whatsnew-head.rst: Document branch
14:32
CountryNerd has quit [Quit: CountryNerd]
15:05
junna has quit [Ping timeout: 268 seconds]
15:19
jcea has joined #pypy
15:26
<
arigato >
a python gotcha: if d is a dict, the line "d = d[key] = {}" doesn't do what you think
15:30
<
Alex_Gaynor >
arigato: pfff, what do I think it does :-)
15:30
<
arigato >
it's meant to do "d1 = {}; d[key] = d1; d = d1"
15:31
<
arigato >
except it's doing something different
15:31
<
arigato >
better just write it explicitly
15:31
<
Alex_Gaynor >
yes, indeed.
15:32
<
arigato >
what it
*does* is "d = {}; d[key] = d"
15:32
<
arigato >
which is a bit unexpected
15:33
<
arigato >
I guess I could write it like this: d[key] = d = {}
15:33
<
arigato >
that's very high on the obscure side though
15:34
<
Alex_Gaynor >
it's all obscure :-) in C it would be undefined behavior to both write and read to one variable without a sequence point :P
15:36
<
mattip >
So the assignments in `a = b = c = d = None` are done left to right, not right to left?
15:38
<
mattip >
dis.dis agrees, first a, then b, then c, then d using a DUP_TOP bytecode to duplicate the None value
15:40
<
arigato >
it's at least consistent with: e = {}; d, d["key"] = e, e
15:40
<
arigato >
which also evaluates the d["key"] with the value of d already modified to be equal to e
15:49
tsaka__ has joined #pypy
15:50
tsaka_ has quit [Read error: No route to host]
15:57
adamholmberg has joined #pypy
15:59
jvesely has joined #pypy
16:05
junna has joined #pypy
16:07
adamholmberg has quit [Remote host closed the connection]
16:11
adamholmberg has joined #pypy
16:13
marky1991 has joined #pypy
16:18
adamholmberg has quit [Remote host closed the connection]
16:20
marky1991 has quit [Ping timeout: 268 seconds]
16:20
adamholmberg has joined #pypy
16:24
adamholmberg has quit [Remote host closed the connection]
16:26
adamholmberg has joined #pypy
16:34
idnar has joined #pypy
16:39
dddddd has joined #pypy
16:41
avakdh has joined #pypy
16:42
stillinbeta has quit []
16:42
stillinbeta has joined #pypy
16:44
adamholmberg has quit [Remote host closed the connection]
17:09
marky1991 has joined #pypy
17:12
junna has quit [Ping timeout: 268 seconds]
17:36
i9zO5AP has joined #pypy
17:39
Ai9zO5AP has quit [Ping timeout: 250 seconds]
17:42
dddddd has quit [Ping timeout: 240 seconds]
17:54
dddddd has joined #pypy
18:41
stillinbeta has quit []
18:44
avakdh has joined #pypy
18:44
stillinbeta has joined #pypy
19:23
adamholmberg has joined #pypy
19:27
adamholmberg has quit [Remote host closed the connection]
20:13
lazka has joined #pypy
20:14
<
lazka >
mattip, in case it hasn't been reported, SSL is broken for the rc release. On Ubuntu at least
20:14
<
mattip >
how is it broken?
20:14
<
mattip >
which ubuntu?
20:14
<
lazka >
Ubuntu 19.10
20:15
<
mattip >
thanks for the report
20:15
<
lazka >
the squeaky builds work
20:16
<
mattip >
hmm, can reproduce on 18.04 as well :(
20:17
<
mattip >
fails with <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed>
20:21
<
mattip >
probably we need to apply the ssl patches from portable-pypy
20:27
<
mattip >
lazka: thanks, indeed the portable-pypy patches fix it
20:28
<
lazka >
all my other tests work as before (only PyOS_FSPath() still missing)
20:32
<
lazka >
ok, cool :) bye
20:32
lazka has quit [Remote host closed the connection]
20:32
<
mattip >
thanks. The file squeaky patches the CPython ssl.py. I wonder if we should be fixing the cffi _ssl.py instead
20:45
jvesely has quit [Quit: jvesely]
20:46
lazka has joined #pypy
20:49
jcea has quit [Remote host closed the connection]
20:49
<
lazka >
mattip, I think the SSL_CERT_FILE/SSL_CERT_DIR are also build time constants in openssl, so it would make sense that a portable build would ignore them
20:49
jcea has joined #pypy
20:49
<
lazka >
while a system build wouldn't
20:51
lazka has quit [Remote host closed the connection]
21:24
<
arigato >
ronan: if issue 3096 is still fixed with your pull request, I have nothing against it
21:29
marky1991 has quit [Read error: Connection reset by peer]
21:32
<
arigato >
I guess I'm not understanding why it fails CPython's own tests given that the code you revert tries to follow more closely what CPython does
21:32
<
arigato >
but I'm fine with the pull request anyway
21:33
<
arigato >
it's typically the kind of thing where CPython and PyPy would always differ very subtly, just because what CPython really does is unexplainable in more abstract terms
21:58
Kipras_ has joined #pypy
22:12
ljwobker has joined #pypy
22:15
ljwobker has quit [Remote host closed the connection]
22:30
<
ronan >
arigato: well, in my understanding, the code before your changes was actually closer to CPython, since it doesn't have an error stack
23:10
Kipras_ has quit [Ping timeout: 240 seconds]
23:48
jcea has quit [Remote host closed the connection]
23:49
jcea has joined #pypy
23:50
lritter has quit [Quit: Leaving]
23:51
tsaka__ has quit [Read error: Connection reset by peer]