projects / oota-llvm.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 2b17108) | patch
Calling memmove on a MachineOperand is totally safe.
authorBenjamin Kramer <benny.kra@googlemail.com>
Sat, 21 Feb 2015 16:22:48 +0000 (16:22 +0000)
committerBenjamin Kramer <benny.kra@googlemail.com>
Sat, 21 Feb 2015 16:22:48 +0000 (16:22 +0000)
commit7efcb3338cbabc9a5cdccf27a36e1c18889069f3
tree7da6a5cff721a093025b98bb6e1e9e5096c5e053tree | snapshot
parent2b171080644b1747d4a7dc0741e93a9fd4634f38commit | diff
Calling memmove on a MachineOperand is totally safe.

While it's not POD due to the user-defined constructor, it's still a trivially
copyable type. No functional change.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@230141 91177308-0d34-0410-b5e6-96231b3b80d8
lib/CodeGen/MachineInstr.cpp diff | blob | history
C/C++ LLVM-based compilers that forbids OOTA behaviors