Displaying 4 results from an estimated 4 matches for "58688".
Did you mean:
5688
2009 Jun 30
3
[LLVMdev] JIT allocates global data in function body memory
...dn't find the author
(johannes) on IRC so ssen told me to ask LLVMdev about this behavior.
There's even a patch to work around this behavior on Apple ARM
platforms:
http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/ExecutionEngine/JIT/JIT.cpp?view=diff&pathrev=72630&r1=58687&r2=58688
So what should the right long-term behavior be? It makes sense to me
to use the JITMemoryManager for this so that clients of the JIT can
customize allocation instead of using malloc or new char[]. On the
other hand, that complicates the API and requires a homegrown malloc
implementation in the D...
2006 Apr 01
0
CESA-2006:0101 Important CentOS 4 i386 kernel - security update
CentOS Errata and Security Advisory 2006:0101
https://rhn.redhat.com/errata/RHSA-2006-0101.html
The following updated files have been uploaded and are currently
syncing to the mirrors:
i386:
kernel-2.6.9-22.0.2.EL.i586.rpm
kernel-2.6.9-22.0.2.EL.i686.rpm
kernel-devel-2.6.9-22.0.2.EL.i586.rpm
kernel-devel-2.6.9-22.0.2.EL.i686.rpm
kernel-doc-2.6.9-22.0.2.EL.noarch.rpm
2018 Nov 15
1
libvirt call qemu to create vm need more than 10 seconds
...7f822c006560 stdioLogD=1
Line 58686: 2018-11-13 14:22:30.130+0000: 95225: debug : virNetSocketNewConnectUNIX:640 : path=/var/run/libvirt/virtlogd-sock spawnDaemon=0 binary=<null>
Line 58687: 2018-11-13 14:22:30.130+0000: 95225: debug : virNetSocketNewConnectUNIX:704 : connect() succeeded
Line 58688: 2018-11-13 14:22:30.130+0000: 95225: debug : virNetSocketNew:236 : localAddr=0x7f8244ca5530 remoteAddr=0x7f8244ca55c0 fd=20 errfd=-1 pid=0
Line 58689: 2018-11-13 14:22:30.130+0000: 95225: info : virObjectNew:202 : OBJECT_NEW: obj=0x7f822c00aab0 classname=virNetSocket
Line 58690: 2018-11-13 14:22:3...
2009 Jun 30
0
[LLVMdev] JIT allocates global data in function body memory
...work. If you
want to generalize it so other models work as well, go ahead.
> There's even a patch to work around this behavior on Apple ARM
> platforms:
> http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/ExecutionEngine/JIT/JIT.cpp?view=diff&pathrev=72630&r1=58687&r2=58688
>
> So what should the right long-term behavior be? It makes sense to me
> to use the JITMemoryManager for this so that clients of the JIT can
> customize allocation instead of using malloc or new char[]. On the
> other hand, that complicates the API and requires a homegrown malloc...