- Give it a shorter name (because we're going to refer to it often from SelectionDAG and friends).
- Specialize FlagsEnumTraits for it, so we can do bitwise ops on it without losing type information.
- Make some enum values constants in MachineMemOperand instead. MOMaxBits should not be a valid Flag.
- Simplify some of the bitwise ops for dealing with Flags.
Outside of the enum I find it more dangerous that those are forgotten when someone updates the enum.
I also wanted to point out that we can solve target flags in a slightly more elegant way. Though we should change one thing at a time and better leave this bit for another day/patch:
in target code: