Displaying 3 results from an estimated 3 matches for "d40975".
Did you mean:
d40375
2019 Jan 18
2
Aliasing rules difference between GCC and Clang
...goals behind the new TBAA is to be able to accurately
> represent various kinds accesses to subobjects. This includes
> non-constant-indexed accesses to array elements. More info on how such
> accesses are supposed to be represented can be found here:
>
> https://reviews.llvm.org/D40975
>
> If that's what you need, then the new TBAA info seems to be the most
> promising option. But please note that it's still a work in progress
> and is not mature enough for production use.
>
> Hope this helps.
>
> Regards,
>
>
> On 14/01/2019 15:57, Jona...
2019 Jan 14
2
Aliasing rules difference between GCC and Clang
Hi,
It was a while now since I first asked about TBAA, and I am now getting
back to this, trying to understand TBAA as it seems that the issue I
described earlier originally in this thread is still one of many "TODO"s
in CGExpr.cpp
(http://lists.llvm.org/pipermail/llvm-dev/2018-September/126290.html).
I would like to help on this to the best of my abilities, but I'm not
quite
2017 Nov 02
2
RFC: Generate plain !tbaa tags in place of !tbaa.struct ones
On 02/11/17 05:54, Hal Finkel wrote:
>
> On 10/31/2017 05:02 AM, Ivan Kosarev wrote:
>> To clarify further, what this paper proposes is to use !tbaa for all
>> kinds of accesses, including aggregate ones, so we don't need to
>> bother trying to convert them when an aggregate access becomes a
>> series of scalar accesses or vice versa. As I said, in most cases