[llvm] AMDGPU/GlobalISel: Use integer as MMO type for loads and stores lowering (PR #210096)

[LLVM Continuous Integration via llvm-commits]

llvm-ci wrote:

LLVM Buildbot has detected a new failure on builder `llvm-x86_64-debian-dylib` running on `gribozavr4` while building `llvm` at step 6 "test-build-unified-tree-check-clang".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/60/builds/4592

<details>
<summary>Here is the relevant piece of the build log for the reference</summary>

```
Step 6 (test-build-unified-tree-check-clang) failure: test (failure)
******************** TEST 'Clang :: ClangScanDeps/logging-two-threads.c' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 5
rm -rf /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp
# executed command: rm -rf /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp
# RUN: at line 6
split-file /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp
# executed command: split-file /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp
# RUN: at line 7
sed -e "s|DIR|/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp|g" /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/cdb.json.template > /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/cdb.json
# executed command: sed -e 's|DIR|/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp|g' /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/cdb.json.template
# RUN: at line 9
/b/1/llvm-x86_64-debian-dylib/build/bin/clang-scan-deps -compilation-database /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/cdb.json    -format experimental-full -log-path=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log -j 2 -o /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/deps.json
# executed command: /b/1/llvm-x86_64-debian-dylib/build/bin/clang-scan-deps -compilation-database /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/cdb.json -format experimental-full -log-path=/b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log -j 2 -o /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/deps.json
# RUN: at line 13
/b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=TU1 < /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log
# executed command: /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=TU1
# RUN: at line 14
/b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=TU2 < /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log
# executed command: /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=TU2
# RUN: at line 24
grep -c "pcm_compile:" /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log | /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=COMPILES
# executed command: grep -c pcm_compile: /b/1/llvm-x86_64-debian-dylib/build/tools/clang/test/ClangScanDeps/Output/logging-two-threads.c.tmp/scan.log
# executed command: /b/1/llvm-x86_64-debian-dylib/build/bin/FileCheck /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c --check-prefix=COMPILES
# .---command stderr------------
# | /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c:27:14: error: COMPILES: expected string not found in input
# | // COMPILES: {{^2$}}
# |              ^
# | <stdin>:1:1: note: scanning from here
# | 3
# | ^
# | 
# | Input file: <stdin>
# | Check file: /b/1/llvm-x86_64-debian-dylib/llvm-project/clang/test/ClangScanDeps/logging-two-threads.c
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |             1: 3 
# | check:27'0    {  } search range (exclusive bounds)
# | check:27'1         error: no match found in search range
# | >>>>>>
# `-----------------------------
# error: command failed with exit status: 1

--
...

```

</details>

https://github.com/llvm/llvm-project/pull/210096