similar to: [LLVMdev] LLVM C bindings

Corrado Zoccolo wrote: > Unfortunately, it seems that llvm-c interface lacks major > functionalities, e.g. getting a pointer to a jit-ted function. > It is easy to write a small c++ wrapper to expose the functionality > that one wants (llvm-py does it for the many optimization passes not > available through c binding), but I wonder if it is possible to have a > simpler &

On Mon, 16 Feb 2009 21:18:48 +0000 Jon Harrop <jon at ffconsultancy.com> wrote: > > On Monday 16 February 2009 20:04:38 Paul Melis wrote: > Yes. I similarly found that tail calls, sret and parts of first-class structs > are not usable from OCaml and much of the functionality was not implemented > in the C API in LLVM 2.4. > >> SWIG (www.swig.org) recently added a C

It looks fine to me. Anton, does it look ok to you? Evan On Mar 20, 2009, at 2:33 PM, Corrado Zoccolo wrote: > I've created a patch (attached to the bug): > http://llvm.org/bugs/attachment.cgi?id=2744, that goes in a different > direction, and solves the safety problems. > The patch uses original asm, but removes the call through plt, and > puts the invoked function in an

On Mar 11, 2009, at 2:39 PM, Corrado Zoccolo wrote: > I don't know how to file a PR, but I have a patch (see below), that > should work regardless of abi differences, since it relies on the > compiler to do the though job. > > void X86CompilationCallback_SSE(void) { > char * SAVEBUF= (char*) alloca(64+12); // alloca is 16byte aligned How do you ensure it's 16-byte

On Linux x86_64, it is different. The x86-64 ABI says (http://www.x86-64.org/viewvc/trunk/x86-64-ABI/low-level-sys-info.tex?revision=84&content-type=text%2Fplain): >> The end of the input argument area shall be aligned on a 16 byte boundary. In other words, the value (%rsp - 8) is always a multiple of 16 when control is transferred to the function entry point. The stack pointer, %rsp,

I don't know how to file a PR, but I have a patch (see below), that should work regardless of abi differences, since it relies on the compiler to do the though job. void X86CompilationCallback_SSE(void) { char * SAVEBUF= (char*) alloca(64+12); // alloca is 16byte aligned asm volatile ( "movl %%eax,(%0)\n" "movl %%edx,4(%0)\n" // Save EAX/EDX/ECX

Hello. I found that the X86CompilationCallback_SSE wrapper for X86CompilationCallback2 is not setting up properly for the PIC invocation. Before you can correctly invoke a function via the Procedure Linkage Table (plt), the ABI mandates that ebx is pointing to the GOT (Global Offset Table) (see http://www.greyhat.ch/lab/downloads/pic.html) Dump of assembler code for function

Hi Evan > It looks fine to me. Anton, does it look ok to you? This looks ok for me modulo win64+vcpp issues, which I mentioned in the PR (external .asm files). The anonymous namespace thing should be guarded by define (either _M_AMD64 or X86_64_JIT && _MSC_VER, I'd prefer the latter). -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint

Hi, I found that on my system: $ uname -a Linux tintoretto 2.6.23.8cz #1 SMP Fri Nov 23 17:07:39 CET 2007 x86_64 Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz GNU/Linux $ cat /etc/redhat-release Mandriva Linux release 2008.0 (Official) for x86_64 I can't execute functions Jitted by LLVM that call back functions in the main program, if the jit is run from a .so library. I replaced LLVM with

Hello, Simon > So far, i found no way to denote calls to the host function as aligned > or maintain stack alignment throughout the stack frame of the jit > compiled function. Further, the gcc front end (llvm-g++ (GCC) 4.2.1) > seems to ignore directives such as -mpreferred-stack-boundary. Mike is right. It depends on your subtarget: 1. If you're running stuff on Darwin, which has

Hi all, i am trying to call an aligned function in my host application from jit compiled bitcode. The call itself is done using an absolute pointer to the function. The host application's functions make heavy use of SSE instructions and are thus operate on a stack aligned to 16 byte. If i call an aligned function in the host application from a frame running jit compiled code, the alignment

On Thu, Mar 12, 2009 at 5:18 PM, Dan Gohman <gohman at apple.com> wrote: > This looks like an interesting idea. As written, the inline asms > aren't safe > though; they reference %eax, %edx, etc. without declaring such things in > constraints, so the compiler wouldn't know that it can't clobber those > registers. > > Dan > I don't know how to specify

I've created a patch (attached to the bug): http://llvm.org/bugs/attachment.cgi?id=2744, that goes in a different direction, and solves the safety problems. The patch uses original asm, but removes the call through plt, and puts the invoked function in an anonymous namespace. This allows the static linker to always know the location of the jump, removing the need for PIC invocation setup. This

Hi again, >From a .so, I'm doing the following: * I create an empty Module, declare some functions (from the main executable) and add a global mapping for them. * Then I create a jitted function that calls those global functions * and I call it. The JITted function segfaults because x86_64 JIT creates a call with 32bit relative address to rip, while the called function is outside reach.

This looks like an interesting idea. As written, the inline asms aren't safe though; they reference %eax, %edx, etc. without declaring such things in constraints, so the compiler wouldn't know that it can't clobber those registers. Dan On Mar 11, 2009, at 2:39 PM, Corrado Zoccolo wrote: > I don't know how to file a PR, but I have a patch (see below), that > should work

Dear R-lings, I did not know which list to post to, because it is a studentship so not really a job, so it did not fit the r-sig-jobs list .... and it is about devloping an extension package interfaced with R .... I hope I did not upset anyone. If so apologies. The Centre For Complex systems Analysis at the University of York (YCCSA) in UK in collaboration with Stockholm Environment

here my smb.conf [global]         netbios name = DC1         realm = LXDOM.COM         server role = active directory domain controller         workgroup = LXDOM         idmap_ldb:use rfc2307 = yes         log level = 1         log file = /usr/local/samba/var/log.%m Il 29/11/2018 12:43, Rowland Penny via samba ha scritto: > On Thu, 29 Nov 2018 12:34:29 +0100 > Corrado

Hello Luis tomorrow i'm not in office, reply to you thursday One question : who is owner and whats rights for dir     /home     /home/samba     /home/samba/sysvol because, from windows client, user into domain admins, when i change in security tab, explorer always crash bye Il 06/11/2018 17:16, L.P.H. van Belle via samba ha scritto: > Ok, next, > > From a windows pc connect to

Il 31/10/2018 17:18, Rowland Penny via samba ha scritto: >> ok, this smb.conf is default from classicupgrade > I am fairly sure it isn't. ok, i did many changes and cut&paste. You are the expert !! :-) > >> i take out they >>> Do you really need an insecure auth method ? >> why ?? > You have set 'ntlm auth = yes', this allows you to use an

Il 26/10/2018 13:45, Rowland Penny via samba ha scritto: > ldbsearch -Hldap://$(hostname -s) -k yes -P '(&(samaccountname=Domain > Users)(gidNumber=*))' gidNumber | grep gidNumber | awk '{print $NF}' sorry but nothing happen [root at dc1 ~]# ldbsearch -H ldap://$(hostname -s) -k yes -P '(&(samaccountname=Domain Users)(gidNumber=*))' gidNumber | grep