Displaying 4 results from an estimated 4 matches for "hopefolli".
Did you mean:
hopefolly
2012 Oct 28
2
[LLVMdev] Annotating known pointer alignment
Hi Duncan,
thanks for your comments.
>> First, consider this function:
>> #include <stdint.h>
>> uint64_t foo(uint64_t *bar) {
>> *bar = 42;
>> return (uint64_t)bar & 3;
>> }
>>
>> Which is compiled to
>> define i64 @foo(i64* %bar) nounwind uwtable ssp {
>> store i64 42, i64* %bar, align 8
>>
2012 Oct 29
0
[LLVMdev] Annotating known pointer alignment
Hi Clemens,
> thanks for your comments.
>
>>> First, consider this function:
>>> #include <stdint.h>
>>> uint64_t foo(uint64_t *bar) {
>>> *bar = 42;
>>> return (uint64_t)bar & 3;
>>> }
>>>
>>> Which is compiled to
>>> define i64 @foo(i64* %bar) nounwind uwtable ssp {
2012 Oct 28
0
[LLVMdev] Annotating known pointer alignment
Hi Clemens,
> I'm instrumenting IR by replacing loads and stores by calls to a library, which
> I have compiled to bitcode such that inlining can take place. My problem is: If
> I could retain the alignment information on the load/store, this would open many
> optimization opportunities after inlining. Unfortunately, I don't know how.
>
> After thinking about it, and
2012 Oct 28
2
[LLVMdev] Annotating known pointer alignment
Hi all,
I'm instrumenting IR by replacing loads and stores by calls to a
library, which I have compiled to bitcode such that inlining can take
place. My problem is: If I could retain the alignment information on the
load/store, this would open many optimization opportunities after
inlining. Unfortunately, I don't know how.
After thinking about it, and trying different things, I now