https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114499
Bug ID: 114499
Summary: MVE: scatter base offset constraints incorrect
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #8 from Kevin Bracey ---
I'm only testing on the Linux trunk because it's what Godbolt has. If it has
bare-metal, I'm not seeing it.
Actual real development system is bare-metal using Arm's embedded GCC releases,
and I don't have a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #6 from Kevin Bracey ---
Retesting the Godbolt on trunk, it's now worse - every line produces multiple
not-very-informative errors:
source>:7:9: error: '_Generic' specifies two compatible types
7 | x = vmulq(x, 0.5); // ok
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #4 from Kevin Bracey ---
Yes, looking at them it seems clear those patches address what I'm seeing with
the `vmulq(x, 6)` issue.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
--- Comment #2 from Kevin Bracey ---
I've just spotted another apparent generic selection problem in my reproducer
for bug 107714 - should I create a new issue for it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Kevin Bracey changed:
What|Removed |Added
CC||stammark at gcc dot gnu.org
--- Comment
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?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714
Bug ID: 107714
Summary: MVE: Invalid addressing mode generated for VLD2
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107515
Bug ID: 107515
Summary: MVE: Generic functions do not accept _Float16 scalars
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Co
11 matches
Mail list logo
