Displaying 4 results from an estimated 4 matches for "tbba".
Did you mean:
tbaa
2016 Feb 03
2
[buildSchedGraph] memory dependencies
...loads from the stores. In the MF I see
...
%vreg32<def> = L %vreg0, 56, %noreg;
mem:LD4[%src1(align=64)+56](align=8)(tbaa=!1) GR32Bit:%vreg32
ADDR64Bit:%vreg0
...
ST %vreg33, %vreg1, 60, %noreg;
mem:ST4[%dest(align=64)+60](align=4)(tbaa=!4) GR32Bit:%vreg33
ADDR64Bit:%vreg1
...
Since the tbba tags are part of the MachineMemOperands, it is easy to
just continue the patch (above isUnsafeMemoryObject() checks) with
+ AAMDNodes AATagsA = MMOa->getAAInfo(), AATagsB = MMOb->getAAInfo();
+ if (AATagsA->TBAA && AATagsB->TBAA && AATagsA != AATagsB)
+ return fal...
2012 Nov 09
0
[LLVMdev] inttoptr and basicaa
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Arnold Schwaighofer
> Subject: [LLVMdev] inttoptr and basicaa
> BasicAA treats it conservatively if used on its own. It will return mayalias
> for the two pointers.
> TBAA operates based on the guarantee that pointers to different types cannot
> alias (think C's strict
2012 Nov 09
2
[LLVMdev] inttoptr and basicaa
BasicAA treats it conservatively if used on its own. It will return
mayalias for the two pointers.
TBAA operates based on the guarantee that pointers to different types
cannot alias (think C's strict aliasing rules).
Therein lies its power but also its danger, that is, nothing prevents the
programmer to write code that violates these rules (That's why we have
-fno-strict-aliasing).
So
2020 Mar 03
2
TBAA for struct fields
[AMD Public Use]
Hi Oliver,
I get rid of the warnings by explicitly type-casting it to struct*, and still get similar results.
#######################################################
struct P {
float f1;
float f2;
float f3[3];
float f4;
};
void foo(struct P* p1, struct P* p2) {
p1->f2 = 1.2;
p2->f1 = 3.7;
}
int callFoo() {
struct P p;
foo(&p,