Displaying 5 results from an estimated 5 matches for "setonlyreadsmemori".
Did you mean:
setonlyreadsmemory
2009 Jul 24
3
[LLVMdev] setOnlyReadsMemory / setDoesNotAccessMemory
Hello,
I'm in a situation where my code is calling many native functions.
Sometimes, these calls are simply calls to static "accessor" methods that
read a variable in some class object (object pointer as input, member
variable value returned as output). I was wondering if using the
setOnlyReadsMemory method on the native function objects could help LLVM
generate optimized code
2015 Dec 03
3
Function attributes for LibFunc and its impact on GlobalsAA
----- Original Message -----
> From: "James Molloy via llvm-dev" <llvm-dev at lists.llvm.org>
> To: "Vaivaswatha Nagaraj" <vn at compilertree.com>
> Cc: "LLVM Dev" <llvm-dev at lists.llvm.org>
> Sent: Thursday, December 3, 2015 4:41:46 AM
> Subject: Re: [llvm-dev] Function attributes for LibFunc and its impact on GlobalsAA
>
>
2009 Jul 24
1
[LLVMdev] setOnlyReadsMemory / setDoesNotAccessMemory
But, which optimization pass will take advantage of those flags?
As for nounwind, that means "can't throw an exception"?
- Maxime
John McCall-2 wrote:
>
> Nyx wrote:
>> Hello,
>>
>> I'm in a situation where my code is calling many native functions.
>> Sometimes, these calls are simply calls to static "accessor" methods that
>>
2009 Jul 24
0
[LLVMdev] setOnlyReadsMemory / setDoesNotAccessMemory
Nyx wrote:
> Hello,
>
> I'm in a situation where my code is calling many native functions.
> Sometimes, these calls are simply calls to static "accessor" methods that
> read a variable in some class object (object pointer as input, member
> variable value returned as output). I was wondering if using the
> setOnlyReadsMemory method on the native function objects
2013 Feb 24
1
[LLVMdev] Optimizer to remove duplicate loads?
On 24/02/13 09:02, Duncan Sands wrote:
> in order to do this, the optimizers need to know that the call to
> @trace_integer does not modify the contents of @pt. Is it logically
> possible for them to deduce this? If not, no optimizer can do what
> you want.
Yeah, I thought about that and then realized in this context they could
not (it's an external function). Is there some