Displaying 4 results from an estimated 4 matches for "autoprepend".
2004 Jun 19
0
[LLVMdev] Problems loading passes on Mac OS X
...s loaded.
I don't know anything about how dynamic object loading works on OS/X
(obviously), but it sounds like it's not running the static constructor.
> Does it assume anything about the symbol names?
I don't know what it will take to get the JIT working on OS/X: it might
have to autoprepend an _. Since we don't (yet) have a PPC JIT, this isn't
an issue though.
-Chris
> On Jun 19, 2004, at 2:07 PM, Chris Lattner wrote:
>
> > On Sat, 19 Jun 2004, Michael McCracken wrote:
> >
> >> Hi, I can't get opt to list (in -help) passes that I load using...
2004 Jun 19
2
[LLVMdev] Problems loading passes on Mac OS X
...ng about how dynamic object loading works on OS/X
> (obviously), but it sounds like it's not running the static
> constructor.
>
>> Does it assume anything about the symbol names?
>
> I don't know what it will take to get the JIT working on OS/X: it might
> have to autoprepend an _. Since we don't (yet) have a PPC JIT, this
> isn't
> an issue though.
>
> -Chris
>
>
>
>> On Jun 19, 2004, at 2:07 PM, Chris Lattner wrote:
>>
>>> On Sat, 19 Jun 2004, Michael McCracken wrote:
>>>
>>>> Hi, I can't ge...
2004 Jun 19
2
[LLVMdev] Problems loading passes on Mac OS X
Unfortunately it's not that easy, although I'd love to fix it if I can
figure out how.
OS X 10.3 does have dlfcn.h and dlopen() - for 10.3, they added the
dlcompat library that uses the OS X NSLink* stuff to support dlopen and
dlsym. configure seems to pick that up fine.
It seems like the code that's there already should work fine, so I'm
not sure where else to look.
I'm
2004 Jun 20
0
[LLVMdev] Problems loading passes on Mac OS X
...ks on OS/X
>> (obviously), but it sounds like it's not running the static
>> constructor.
>>
>>> Does it assume anything about the symbol names?
>>
>> I don't know what it will take to get the JIT working on OS/X: it
>> might
>> have to autoprepend an _. Since we don't (yet) have a PPC JIT, this
>> isn't
>> an issue though.
>>
>> -Chris
>>
>>
>>
>>> On Jun 19, 2004, at 2:07 PM, Chris Lattner wrote:
>>>
>>>> On Sat, 19 Jun 2004, Michael McCracken wrote:
>>...