cfbolz changed the topic of #pypy to: PyPy, the flexible snake (IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end ) | use cffi for calling C | if a pep adds a mere 25-30 [C-API] functions or so, it's a drop in the ocean (cough) - Armin
<larstiq>
not really being involved but having read your earlier discussion with nulano I understand and agree with your motivation there
<Dejan>
mattip, I think it makes sense
oberstet has joined #pypy
<mattip>
thanks
yuiza has quit [Ping timeout: 240 seconds]
muke has joined #pypy
<muke>
Hey, does anyone know anything about problems pypy might have with directly making syscalls? I'm building an llvm backend and trying to use it's memcpy function through the API, and doing so causing the compilation of the IR to fail and pypy to print this to stderr:
<muke>
JIT session error: Symbols not found: [ memcpy ]
<muke>
doing the same thing in a regular C program works fine, though
<nimaje>
(afaik memcpy isn't a syscall, but a normal function)
<muke>
oh, sorry, conflating libc and kernel space :p
Gustavo6046 has joined #pypy
nopf_ is now known as nopf
<tumbleweed>
mattip: thanks, will do
oberstet has quit [Quit: Leaving]
_whitelogger has joined #pypy
<cfbolz>
muke: that's like a problem specific to llvm's jit mode?
dustinm has quit [Quit: Leaving]
dustinm has joined #pypy
lritter has quit [Ping timeout: 265 seconds]
<muke>
cfbolz Yea, but again only when run through rpython - I was wondering if maybe the rffi might be getting in the way somehow in terms of what llvm can 'see' for symbols
<muke>
figured out the error is definetly coming from llvm and not pypy though so I'll ask the llvm people about it and see what info they have too