aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@sifive.com>2021-01-11 19:58:35 -0800
committerCraig Topper <craig.topper@sifive.com>2021-01-11 19:58:47 -0800
commitb1c304c4946506c0d00532829fb2f91276dde0c8 (patch)
treefd7557ac5942f2a8b7bff4437a8c8a3c53735928 /clang/lib/Frontend/CompilerInvocation.cpp
parente5b4dbab041f6692b8c5286406e2566be87feac9 (diff)
downloadllvm-b1c304c4946506c0d00532829fb2f91276dde0c8.zip
llvm-b1c304c4946506c0d00532829fb2f91276dde0c8.tar.gz
llvm-b1c304c4946506c0d00532829fb2f91276dde0c8.tar.bz2
[CodeGen] Try to make the print of memory operand alignment a little more user friendly.
Memory operands store a base alignment that does not factor in the effect of the offset on the alignment. Previously the printing code only printed the base alignment if it was different than the size. If there is an offset, the reader would need to figure out the effective alignment themselves. This has confused me before and someone else was recently confused on IRC. This patch prints the possibly offset adjusted alignment if it is different than the size. And prints the base alignment if it is different than the alignment. The MIR parser has been updated to read basealign in addition to align. Reviewed By: arsenm Differential Revision: https://reviews.llvm.org/D94344
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions