[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2023-01-16 Thread stammark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Stam Markianos-Wright changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGN

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2023-01-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #8 from CVS Commits --- The releases/gcc-12 branch has been updated by Stam Markianos-Wright : https://gcc.gnu.org/g:25edc76f2afba0b4eaf22174d42de042a6969dbe commit r12-9038-g25edc76f2afba0b4eaf22174d42de042a6969dbe Author: Stam Ma

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2023-01-10 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #7 from CVS Commits --- The releases/gcc-11 branch has been updated by Stam Markianos-Wright : https://gcc.gnu.org/g:08842ad274f5e2630994f7c6e70b2d31768107ea commit r11-10461-g08842ad274f5e2630994f7c6e70b2d31768107ea Author: Stam M

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-12-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #6 from CVS Commits --- The master branch has been updated by Stam Markianos-Wright : https://gcc.gnu.org/g:4269a6567eb991e6838f40bda5be9e3a7972530c commit r13-4935-g4269a6567eb991e6838f40bda5be9e3a7972530c Author: Stam Markianos-W

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-12-09 Thread stammark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Stam Markianos-Wright changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Version|12.

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-21 Thread kevin.bracey at alifsemi dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #5 from Kevin Bracey --- I had a look at the GCC source. The vld2/vst2/vld4/vst4 instructions in mve.md have reused the "Um" constraint used for vld/vst in Neon, which permits both "!" and register offset. This needs to be tightened

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-21 Thread kevin.bracey at alifsemi dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #4 from Kevin Bracey --- The assembler's rejection of the vld2 is valid - the only permitted post-indexed form is to use "!" for increment by 32 (the amount read). Experimenting by changing "inStep" you can see the compiler backend

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-17 Thread stammark at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Stam Markianos-Wright changed: What|Removed |Added Last reconfirmed||2022-11-17 --- Comment #3 from

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-16 Thread kevin.bracey at alifsemi dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 Kevin Bracey changed: What|Removed |Added CC||stammark at gcc dot gnu.org --- Comment

[Bug target/107714] MVE: Invalid addressing mode generated for VLD2

2022-11-16 Thread kevin.bracey at alifsemi dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 --- Comment #1 from Kevin Bracey --- Looking at that assembly output from Compiler Explorer, I'm also at a loss as to what happened to the "6" for the VMUL. Maybe something else to look at?