[llvm-dev] Aliasing rules difference between GCC and Clang (original) (raw)
Jonas Paulsson via llvm-dev llvm-dev at lists.llvm.org
Tue Jan 22 06:02:25 PST 2019
- Previous message: [llvm-dev] Aliasing rules difference between GCC and Clang
- Next message: [llvm-dev] Aliasing rules difference between GCC and Clang
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Ivan,
On 2019-01-18 10:15, Ivan Kosarev wrote:
IIRC, there were proposals/attempts to represent accesses to array elements as accesses to their first elements, which can technically be encoded with the current TBAA format and thus may work as an incremental improvement on top of the existing TBAA machinery you are looking for. But this may need making sure there will be no regressions for some tricky cases like those that involve GCC's type punning and changing effective types within unions and in dynamic memory. It would be interesting for me to apply such a patch and evaluate if it really helps my test case. I would much appreciate any links to (or files of) your patches and the attempts you mentioned above.
Thanks,
Jonas
- Previous message: [llvm-dev] Aliasing rules difference between GCC and Clang
- Next message: [llvm-dev] Aliasing rules difference between GCC and Clang
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]