Displaying 3 results from an estimated 3 matches for "addr_b".
Did you mean:
addr_t
2018 Mar 19
4
RFC: Devirtualization v2
...llvm.invariant.group.barrier.The pointer comparison will now not be an
issue, because the optimizer will not be able to replace the operand of a
virtual pointer load with another pointer:%vtable_a = load i8* %a,
!invariant.group !{};;;; %a == %b%addr_a = call i8*
@llvm.strip.invariant.group(i8* %a)%addr_b = call i8*
@llvm.strip.invariant.group(i8* %b)%bool = icmp %addr_a, %addr_bbr %bool,
%if, %afterif:; This will not be able to change %b to %a%vtable_b = load
i8* %b, !invariant.group !{}It is important to notice that vtable load of
%b cannot be replaced with a load of %addr_b Although the optimizer...
2018 Mar 28
0
[cfe-dev] RFC: Devirtualization v2
...omparison will now not be an issue, because the optimizer will not be able to replace the operand of a virtual pointer load with another pointer:
>
>
> %vtable_a = load i8* %a, !invariant.group !{}
> ;;;
> ; %a == %b
> %addr_a = call i8* @llvm.strip.invariant.group(i8* %a)
> %addr_b = call i8* @llvm.strip.invariant.group(i8* %b)
> %bool = icmp %addr_a, %addr_b
> br %bool, %if, %after
> if:
> ; This will not be able to change %b to %a
> %vtable_b = load i8* %b, !invariant.group !{}
>
> It is important to notice that vtable load of %b cannot be replaced wit...
2018 Mar 29
2
[cfe-dev] RFC: Devirtualization v2
....barrier.The pointer comparison will now not be an
> issue, because the optimizer will not be able to replace the operand of a
> virtual pointer load with another pointer:%vtable_a = load i8* %a,
> !invariant.group !{};;;; %a == %b%addr_a = call i8*
> @llvm.strip.invariant.group(i8* %a)%addr_b = call i8*
> @llvm.strip.invariant.group(i8* %b)%bool = icmp %addr_a, %addr_bbr %bool,
> %if, %afterif:; This will not be able to change %b to %a%vtable_b = load
> i8* %b, !invariant.group !{}It is important to notice that vtable load of
> %b cannot be replaced with a load of %addr_b Al...