Displaying 3 results from an estimated 3 matches for "readcycl".
Did you mean:
read_acl
2008 Oct 31
2
[LLVMdev] Optimizations and debug info
...in optimized code:
Hey, your program crashed somewhere in function foo in foo.o
vs.
Hey, your program crashed in function foo in region foo1.c:100 - foo1.c:120
Also preserving debug info about variable names can be useful.
http://nondot.org/sabre/LLVMNotes/EmbeddedMetadata.txt
> For llvm.readcyclecounter, I think it's fine to inhibit
> optimizations. It's hard to understand what it means if it
> doesn't :-). Do you have an example where being able to
> do optimizations would be useful?
>
> Dan
>
I don't have a real example for the readcycles, but I coul...
2008 Nov 03
0
[LLVMdev] Optimizations and debug info
...em attribute time samples to
source lines (even if inherently fuzzy).
> Also preserving debug info about variable names can be useful.
>
> http://nondot.org/sabre/LLVMNotes/EmbeddedMetadata.txt
See also:
http://nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt
:)
>> For llvm.readcyclecounter, I think it's fine to inhibit
>> optimizations. It's hard to understand what it means if it
>> doesn't :-). Do you have an example where being able to
>> do optimizations would be useful?
>>
> I don't have a real example for the readcycles, but I c...
2008 Nov 03
2
[LLVMdev] Optimizations and debug info
...erving debug info about variable names can be useful.
>>
>> http://nondot.org/sabre/LLVMNotes/EmbeddedMetadata.txt
>>
>
> See also:
> http://nondot.org/sabre/LLVMNotes/DebugInfoImprovements.txt
>
> :)
>
>
Thanks for the pointer.
>>> For llvm.readcyclecounter, I think it's fine to inhibit
>>> optimizations. It's hard to understand what it means if it
>>> doesn't :-). Do you have an example where being able to
>>> do optimizations would be useful?
>>>
>>>
>> I don't have a...