diff options
| author | zhijian lin <zhijian@ca.ibm.com> | 2025-11-10 13:30:40 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-11-10 10:30:40 -0800 |
| commit | ccedf259fc0877873cd337deb87b135dfaac753d (patch) | |
| tree | cdc6e966e20d3b749b82a467b4d3f622f5589dda /lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedFrameProviderPythonInterface.cpp | |
| parent | 6d1831361fad0df0b1a36e4ff028de54cb05a6bb (diff) | |
[PowerPC] convert memmove to milicode call .___memmove64[PR] in 64-bit mode (#167334)
conversion of bl memmove call to milicode bl .___memmove64[PR] in
64--bit mode is broken , the patch fix the problem.
in the llvm/include/llvm/IR/RuntimeLibcalls.td, we do not need to define
the
`def ___memmove64 : RuntimeLibcallImpl<MEMCPY>` in PPC64AIXCallList
` def ___memmove32 : RuntimeLibcallImpl<MEMCPY>` in PPC32AIXCallList
since there is function
```
/// Return a function impl compatible with RTLIB::MEMCPY, or
/// RTLIB::Unsupported if fully unsupported.
RTLIB::LibcallImpl getMemcpyImpl() const {
RTLIB::LibcallImpl Memcpy = getLibcallImpl(RTLIB::MEMCPY);
if (Memcpy == RTLIB::Unsupported) {
// Fallback to memmove if memcpy isn't available.
return getLibcallImpl(RTLIB::MEMMOVE);
}
return Memcpy;
}
```
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedFrameProviderPythonInterface.cpp')
0 files changed, 0 insertions, 0 deletions
