A v4i32 insert of an extract can become a simple lane move, as opposed to round-tripping via a GPR. This adds a patterns that turns an v4i32 insert-extract pair into a EXTRACT_SUBREG/INSERT_SUBREG, with the required COPY_TO_REGCLASS. These get better optimized into a simple lane move by the rest of the backed.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Looks like a nice change to me.
llvm/lib/Target/ARM/ARMInstrMVE.td | ||
---|---|---|
1857 | Nit: looks like there is a precedent above, and that this is exceeding 80 columns. |
llvm/lib/Target/ARM/ARMInstrMVE.td | ||
---|---|---|
1857 | Oof. I was worried you were going to say something like that. Some of these patterns do not fit well into 80 lines. I'll see what I can do. |
llvm/lib/Target/ARM/ARMInstrMVE.td | ||
---|---|---|
1857 | Well, do we actually have a coding style for tablegen? |
Nit: looks like there is a precedent above, and that this is exceeding 80 columns.