[all-commits] [llvm/llvm-project] ee407e: [flang] AliasAnalysis: More formally define and di...

[Renaud Kauffmann via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: ee407e17a3a4986bab49272665abc9973d78691d
      https://github.com/llvm/llvm-project/commit/ee407e17a3a4986bab49272665abc9973d78691d
  Author: Renaud Kauffmann <50748669+Renaud-K at users.noreply.github.com>
  Date:   2024-05-16 (Thu, 16 May 2024)

  Changed paths:
    M flang/include/flang/Optimizer/Analysis/AliasAnalysis.h
    M flang/lib/Optimizer/Analysis/AliasAnalysis.cpp
    M flang/lib/Optimizer/Transforms/AddAliasTags.cpp
    M flang/test/Analysis/AliasAnalysis/alias-analysis-2.fir
    M flang/test/Analysis/AliasAnalysis/alias-analysis-3.fir
    A flang/test/Analysis/AliasAnalysis/alias-analysis-9.fir

  Log Message:
  -----------
  [flang] AliasAnalysis: More formally define and distinguish between data and non-data  (#91020)

This PR is an implementation for changes proposed in
https://discourse.llvm.org/t/rfc-distinguish-between-data-and-non-data-in-fir-alias-analysis/78759

Test updates were made when the query was on the wrong reference. So, it
is my hope that this will clear ambiguity on the nature of the queries
from here on.
There are also some TODOs that were addressed. 

It also partly implements what
https://github.com/llvm/llvm-project/pull/87723 is attempting to
accomplish. At least, on a point-to-point query between references, the
distinction is made. To apply it to TBAA, would be another PR.

Note that, the changes were minimal in the TBAA code to retain the
current results.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications