Displaying 3 results from an estimated 3 matches for "__proxy_foo".
Did you mean:
__profd_foo
2007 Oct 23
0
[LLVMdev] me being stupid: me vs the llvm codebase...
On Oct 23, 2007, at 18:19, BGB wrote:
> On Oct 23, 2007, at 11:45, Gordon Henriksen wrote:
>
>> Generally speaking, LLVM neither helps nor hinders here. Maybe
>> someone will follow up with whether the JIT uses stub functions
>> which would enable dynamic relinking If not, it would be a
>> straightforward, if platform-specific, feature to add.
>
> I
2007 Oct 24
2
[LLVMdev] me being stupid: me vs the llvm codebase...
...from the VM, nevermind that any such proxy stubs would be useless though...).
absent special compiler support, this could be implemented more manually with an existing compiler, such as gcc.
example convention:
int Afsd875gSd57g8Th(int x) //invisible autogen name
{
//do something
}
int (*__proxy_foo)(int x)=&Afsd875gSd57g8Th;
int foo(int x) { return(__proxy_foo); }
or (assembler):
section .data
__proxy_foo dd Afsd875gSd57g8Th
section .text
Afsd875gSd57g8Th:
push ebp
mov ebp, esp
..
pop ebp
ret
foo:
jmp [__proxy_foo]
or such...
----- Original Message -----
From: Gordon Henriksen...
2007 Oct 23
2
[LLVMdev] me being stupid: me vs the llvm codebase...
----- Original Message -----
From: "Gordon Henriksen" <gordonhenriksen at mac.com>
To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
Sent: Wednesday, October 24, 2007 1:45 AM
Subject: Re: [LLVMdev] me being stupid: me vs the llvm codebase...
On Oct 23, 2007, at 05:52, BGB wrote:
> I am assuming then that some external assembler is used (such as
>