diff options
| author | Krzysztof Drewniak <Krzysztof.Drewniak@amd.com> | 2024-02-27 09:59:50 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-27 09:59:50 -0600 |
| commit | 4cba5957e6ffdbeb44174d32da892ad09b3eed88 (patch) | |
| tree | d448a312b9e8e3403b90ba5bf3bcc6f9f8750707 /lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp | |
| parent | d612d593eff4af7976250023bbff34d2c10f7526 (diff) | |
| download | llvm-4cba5957e6ffdbeb44174d32da892ad09b3eed88.zip llvm-4cba5957e6ffdbeb44174d32da892ad09b3eed88.tar.gz llvm-4cba5957e6ffdbeb44174d32da892ad09b3eed88.tar.bz2 | |
[mlir][ROCDL] Set the LLVM data layout when lowering to ROCDL LLVM (#74501)
In order to ensure operations lower correctly (especially
memref.addrspacecast, which relies on the data layout benig set
correctly then dealing with dynamic memrefs) and to prevent compilation
issues later down the line, set the `llvm.data_layout` attribute on GPU
modules when lowering their contents to a ROCDL / AMDGPU target.
If there's a good way to test the embedded string to prevent it from
going out of sync with the LLVM TargetMachine, I'd appreciate hearing
about it. (Or, alternatively, if there's a place I could farctor the
string out to).
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/GDBRemoteCommunicationClient.cpp')
0 files changed, 0 insertions, 0 deletions