[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-30 Thread parras at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #15 from Paul-Antoine Arras --- https://godbolt.org/z/dczr15Eo4 Reduced from 538.imagick We get the following assembly: fld fa5,0(a4) vfmv.v.fv2,fa5 vfmacc.vv v1,v3,v2 But since r16-1659-g92e1893e0155b6 we should

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-28 Thread parras at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #14 from Paul-Antoine Arras --- I think the last patchset completes this vector-scalar FMA series - both single-width and widening varieties are now handled. However, before closing this PR, I will carry out a few additional checks o

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-19 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #13 from GCC Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:a0e28fd03f65bb4c76f8eb5ce1e5d56b76897199 commit r16-2361-ga0e28fd03f65bb4c76f8eb5ce1e5d56b76897199 Author: Paul-Antoine Arras Date:

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-14 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #12 from GCC Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:99a3c71db6edb8dc8c426cb2530f9cefbb5bfc9e commit r16-2230-g99a3c71db6edb8dc8c426cb2530f9cefbb5bfc9e Author: Paul-Antoine Arras Date:

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-08 Thread parras at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #11 from Paul-Antoine Arras --- (In reply to Jeffrey A. Law from comment #10) > So I don't mind these changes being tagged to pr119100. My only concern is > how do we know when we're done on this bug? The way I see it is, this bug

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-07-07 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #10 from Jeffrey A. Law --- So I don't mind these changes being tagged to pr119100. My only concern is how do we know when we're done on this bug? We don't need to figure it out right now, but we do need to keep that question in mi

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-06-30 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #9 from GCC Commits --- The master branch has been updated by Paul-Antoine Arras : https://gcc.gnu.org/g:6e24814d9e09019bf42b33b66827648ceff6e7c0 commit r16-1777-g6e24814d9e09019bf42b33b66827648ceff6e7c0 Author: Paul-Antoine Arras

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-06-24 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #8 from GCC Commits --- The master branch has been updated by Jeff Law : https://gcc.gnu.org/g:92e1893e0155b6b3baef2a935efd5936d23a67ea commit r16-1659-g92e1893e0155b6b3baef2a935efd5936d23a67ea Author: Paul-Antoine Arras Date: T

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-06-11 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #7 from GCC Commits --- The master branch has been updated by Paul-Antoine Arras : https://gcc.gnu.org/g:3ada458d344b13a49183278435d372fe9c7fef4b commit r16-1418-g3ada458d344b13a49183278435d372fe9c7fef4b Author: Paul-Antoine Arras

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-06-03 Thread parras at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 Paul-Antoine Arras changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-06-03 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #5 from GCC Commits --- The master branch has been updated by Paul-Antoine Arras : https://gcc.gnu.org/g:b437418bc9547073ec2704398c85c52e060e1fab commit r16-1071-gb437418bc9547073ec2704398c85c52e060e1fab Author: Paul-Antoine Arras

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-03-04 Thread andrew at sifive dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 Andrew Waterman changed: What|Removed |Added CC||andrew at sifive dot com --- Comment

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-03-04 Thread parras at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #3 from Paul-Antoine Arras --- (In reply to Jeffrey A. Law from comment #2) > Paul -- have you run your patch on any design? And if so what did you run > and what was the performance delta before/after? Thanks for your input, Jeff!

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-03-03 Thread law at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #2 from Jeffrey A. Law --- It's even more complicated than that. You have to consider that there can be a cost to move data across the units. ie, it may actually be cheaper to use the variant that broadcasts the value across a vect

[Bug target/119100] RISC-V: missed opportunities for vector-scalar instructions

2025-03-03 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119100 --- Comment #1 from Richard Biener --- doesn't late-combine and/or forwprop not have the single-BB restriction? Also when the vec-duplicate is hoisted out of a loop this then becomes a register pressure in vector vs. scalar regset issue only?