[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-07-24 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 Peter Bergner changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-07-24 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #10 from GCC Commits --- The releases/gcc-12 branch has been updated by Peter Bergner : https://gcc.gnu.org/g:60e513cd47aadd8f139079f8388b14930e6e0913 commit r12-10639-g60e513cd47aadd8f139079f8388b14930e6e0913 Author: Peter Bergner

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-07-23 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #9 from GCC Commits --- The releases/gcc-13 branch has been updated by Peter Bergner : https://gcc.gnu.org/g:bc51e5abcd9cf9a4f74384f2df7c0c8c5ae07c1c commit r13-8939-gbc51e5abcd9cf9a4f74384f2df7c0c8c5ae07c1c Author: Peter Bergner

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-07-22 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #8 from Segher Boessenkool --- (In reply to Peter Bergner from comment #4) > (In reply to Segher Boessenkool from comment #2) > > So, what value do we output? And why? > The invalid offset is zero, so: hashst r0,0(r1) > As the assemb

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-07-22 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #7 from GCC Commits --- The releases/gcc-14 branch has been updated by Peter Bergner : https://gcc.gnu.org/g:33ebeb2435d68ae0546b29394e99e00647943fa9 commit r14-10491-g33ebeb2435d68ae0546b29394e99e00647943fa9 Author: Peter Bergner

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-17 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #6 from Peter Bergner --- Fixed on trunk. I will let it burn-in on trunk for a couple of days before pushing the backports.

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-17 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #5 from GCC Commits --- The master branch has been updated by Peter Bergner : https://gcc.gnu.org/g:c70eea0dba5f223d49c80cfb3e80e87b74330aac commit r15-1377-gc70eea0dba5f223d49c80cfb3e80e87b74330aac Author: Peter Bergner Date: F

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-11 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #4 from Peter Bergner --- (In reply to Segher Boessenkool from comment #2) > So, what value do we output? And why? The invalid offset is zero, so: hashst r0,0(r1) As the assembler mentions, the range of valid offsets is [-512,-8] and

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-11 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #3 from Segher Boessenkool --- (In reply to Segher Boessenkool from comment #2) > So, what value do we output? And why? It would be nice if the assembler told us, btw :-)

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-11 Thread segher at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 --- Comment #2 from Segher Boessenkool --- So, what value do we output? And why?

[Bug target/115389] Invalid ROP hashst offset is emitted when using -mabi=no-altivec

2024-06-07 Thread bergner at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115389 Peter Bergner changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org