aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineTraceMetrics.cpp
diff options
context:
space:
mode:
authorjeanPerier <jperier@nvidia.com>2024-06-27 18:59:03 +0200
committerGitHub <noreply@github.com>2024-06-27 18:59:03 +0200
commit1448ed2000ff0be17025dab0aad7412d054425eb (patch)
treecfce306a3eebe0cca7632116c649bb4635c343e1 /llvm/lib/CodeGen/MachineTraceMetrics.cpp
parent5bbec8f4b6a26e8b4a4209d90a2ad0a0d2416a55 (diff)
downloadllvm-1448ed2000ff0be17025dab0aad7412d054425eb.zip
llvm-1448ed2000ff0be17025dab0aad7412d054425eb.tar.gz
llvm-1448ed2000ff0be17025dab0aad7412d054425eb.tar.bz2
[flang] add extra component information in fir.type_info (#96746)
fir.type does not contain all Fortran level information about components. For instance, component lower bounds and default initial value are lost. For correctness purpose, this does not matter because this information is "applied" in lowering (e.g., when addressing the components, the lower bounds are reflected in the hlfir.designate). However, this "loss" of information will prevent the generation of correct debug info for the type (needs to know about lower bounds). The initial value could help building some optimization pass to get rid of initialization runtime calls. This patch adds lower bound and initial value information into fir.type_info via a new fir.dt_component operation. This operation is generated only for component that needs it, which helps keeping the IR small for "boring" types. In general, adding Fortran level info in fir.type_info will allow delaying the generation of "type descriptors" gobals that are very verbose in FIR and make it hard to work with FIR dumps from applications with many derived types.
Diffstat (limited to 'llvm/lib/CodeGen/MachineTraceMetrics.cpp')
0 files changed, 0 insertions, 0 deletions