Displaying 4 results from an estimated 4 matches for "sloweroperationinform".
Did you mean:
sloweroperationinformer
2007 Apr 13
2
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
And this brings back CommandLine Error: Arugment blah defined more
than once!
And without this, opt -load .../LLVMHello.dylib -hello does not work
on Darwin because dyld is not able to find SlowerOperationInformer ;)
thoughts ?
-
Devang
On Apr 13, 2007, at 11:28 AM, Devang Patel wrote:
>
>
> Changes in directory llvm/lib/Transforms/Hello:
>
> Makefile updated: 1.7 -> 1.8
> ---
> Log message:
>
> Hello uses LLVMSupport.a (SlowerOperationInformer)
>
>
> ---
> D...
2007 Apr 13
0
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
On Fri, 13 Apr 2007, Devang Patel wrote:
> And this brings back CommandLine Error: Arugment blah defined more
> than once!
>
> And without this, opt -load .../LLVMHello.dylib -hello does not work
> on Darwin because dyld is not able to find SlowerOperationInformer ;)
I think libhello should drop its use of SlowOperationInformer.
-Chris
> On Apr 13, 2007, at 11:28 AM, Devang Patel wrote:
>
>>
>>
>> Changes in directory llvm/lib/Transforms/Hello:
>>
>> Makefile updated: 1.7 -> 1.8
>> ---
>> Log message:
&...
2007 Apr 13
3
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
...is Lattner wrote:
> On Fri, 13 Apr 2007, Devang Patel wrote:
>> And this brings back CommandLine Error: Arugment blah defined more
>> than once!
>>
>> And without this, opt -load .../LLVMHello.dylib -hello does not work
>> on Darwin because dyld is not able to find SlowerOperationInformer ;)
>
> I think libhello should drop its use of SlowOperationInformer.
That'll fix Hello example. However, anyone trying to load their custom
pass will likely to run into this again.
-
Devang
2007 Apr 13
0
[LLVMdev] [llvm-commits] CVS: llvm/lib/Transforms/Hello/Makefile
On Fri, 13 Apr 2007, Devang Patel wrote:
>> I think libhello should drop its use of SlowOperationInformer.
>
> That'll fix Hello example. However, anyone trying to load their custom
> pass will likely to run into this again.
It is a long-standing issue. The deal is that libsupport (and many
others) are .a files. If one of the .o files in the .a file is used by a
plugin, but