diff options
author | yonghong-song <yhs@fb.com> | 2024-08-31 10:41:54 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-08-31 10:41:54 -0700 |
commit | 470f55facd083d20d429266de91e4cba15c80ff7 (patch) | |
tree | e8b604c0354874557608bfe7f1cd526c818643d8 /openmp/runtime/src/z_Linux_util.cpp | |
parent | 6d9c6f0ca5957f112b790be479b52ed86950ef12 (diff) | |
download | llvm-470f55facd083d20d429266de91e4cba15c80ff7.zip llvm-470f55facd083d20d429266de91e4cba15c80ff7.tar.gz llvm-470f55facd083d20d429266de91e4cba15c80ff7.tar.bz2 |
[Transforms][IPO] Add remarks for ArgumentPromotion and DeadArgumentE… (#105740)
…limination
ArgumentPromotion and DeadArgumentElimination passes may change function
signature. This makes bpf tracing difficult since users either not aware
of signature change or need to poke into IR or assembly to understand
the function signature change.
This patch enabled to emit some remarks so if recompiling with
-foptimization-record-file=<file>, users can check remarks to see what
kind of signature changes for a particular function. The following are
some examples for implemented remarks:
```
Pass: deadargelim
Name: ReturnValueRemoved
DebugLoc: { File: 'bpf-next/net/mptcp/protocol.c', Line: 572, Column: 0 }
Function: mptcp_check_data_fin
Args:
- String: 'removing return value '
- String: '0'
Pass: deadargelim
Name: ArgumentRemoved
DebugLoc: { File: 'bpf-next/kernel/bpf/syscall.c', Line: 1670, Column: 0 }
Function: map_delete_elem
Args:
- String: 'eliminating argument '
- ArgName: uattr.coerce0
- String: '('
- ArgIndex: '1'
- String: ')'
Pass: argpromotion
Name: ArgumentPromoted
DebugLoc: { File: 'bpf-next/net/mptcp/protocol.h', Line: 570, Column: 0 }
Function: mptcp_subflow_ctx
Args:
- String: 'promoting argument '
- ArgName: sk
- String: '('
- ArgIndex: '0'
- String: ')'
- String: ' to pass by value'
```
[1] https://github.com/llvm/llvm-project/issues/104678
Diffstat (limited to 'openmp/runtime/src/z_Linux_util.cpp')
0 files changed, 0 insertions, 0 deletions