The instcombine code which folds loads and stores into their use types can trip up if the use is a bitcast to a type which we can't directly load or store in the IR. In principle, such types shouldn't exist, but in practice they do today. This is a workaround to avoid a bug while we work towards the long term goal.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Thanks for cleaning up my proposed fix and creating the review. I think this is the correct fix in short term before we can legalize the vector atomic in instruction selection for all backend. LGTM.
Comment Actions
I'd missed the LGTM as the review wasn't accepted. Will commit in the next day or so.