[Bug tree-optimization/118297] not vectorizing some code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118297 --- Comment #9 from Tibor Győri --- > We do apply SLP vectorization with -march=znver3 so I wonder > what you think we are missing (apart from the confusing -fopt-info-missed > messages)? I was not originally thinking GCC was missing anything h

[Bug rtl-optimization/118555] New: -fopt-info reporting of why decide_unroll_constant_iterations decides against unrolling could be improved

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118555 Bug ID: 118555 Summary: -fopt-info reporting of why decide_unroll_constant_iterations decides against unrolling could be improved Product: gcc Version: 15.0

[Bug tree-optimization/118544] -fopt-info misreports unroll factor when using #pragma GCC unroll

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118544 --- Comment #3 from Tibor Győri --- (In reply to Andrew Pinski from comment #2) > The unroll 2 is correct, it was unrolled one time; likewise 3 is unrolled > twice, etc. I suspect you are missunderstanding what the diagnostic is > saying, it is

[Bug tree-optimization/118544] -fopt-info misreports unroll factor when using #pragma GCC unroll

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118544 --- Comment #7 from Tibor Győri --- (In reply to Richard Biener from comment #5) > I suppose cunroll should report the loop was fully peeled. > > Note the unroll amount might be confusig when for example loop header copying > causes the number

[Bug rtl-optimization/118544] New: -fopt-info misreports unroll factor when using #pragma GCC unroll

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118544 Bug ID: 118544 Summary: -fopt-info misreports unroll factor when using #pragma GCC unroll Product: gcc Version: 15.0 URL: https://godbolt.org/z/x1eb65jWf

[Bug tree-optimization/118297] New: vect_analyze_loop_form gets confused by outer loop that only executes its body once

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118297 Bug ID: 118297 Summary: vect_analyze_loop_form gets confused by outer loop that only executes its body once Product: gcc Version: 15.0 URL: https://godbolt.org/z/a5nK

[Bug other/118298] New: Partial unroll request for outer loop with #pragma GCC unroll is silently ignored

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118298 Bug ID: 118298 Summary: Partial unroll request for outer loop with #pragma GCC unroll is silently ignored Product: gcc Version: 15.0 Status: UNCONFIRMED Severi

[Bug other/118295] New: The optimization report says sqrt is not inlinable, even when it does get inlined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118295 Bug ID: 118295 Summary: The optimization report says sqrt is not inlinable, even when it does get inlined Product: gcc Version: 15.0 URL: https://godbolt.org/z/nrqjdh

[Bug other/118295] The optimization report says sqrt is not inlinable, even when it does get inlined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118295 --- Comment #1 from Tibor Győri --- Created attachment 60042 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60042&action=edit Test case -Wall -Wextra -O3 -ffast-math -std=c++20 -march=znver3 -gno-as-loc-support

[Bug tree-optimization/118294] New: GCC doesn't unroll the outer loop of a nest where the outer body trivially only runs once

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118294 Bug ID: 118294 Summary: GCC doesn't unroll the outer loop of a nest where the outer body trivially only runs once Product: gcc Version: 15.0 URL: https://godbolt.org/

[Bug tree-optimization/118294] GCC doesn't unroll the outer loop of a nest where the outer body trivially only runs once

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118294 Tibor Győri changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/58902] small matrix multiplication non vectorized

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58902 Tibor Győri changed: What|Removed |Added CC||tiborgyri at gmail dot com,

[Bug tree-optimization/118297] not vecotrizing some code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118297 --- Comment #6 from Tibor Győri --- (In reply to Andrew Pinski from comment #5) > (In reply to Tibor Győri from comment #4) > > It might even be the case that the current cost model is correct, > > vectorization is indeed sometimes unprofitable.

[Bug other/118295] The optimization report says sqrt is not inlinable, even when it does get inlined

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118295 --- Comment #3 from Tibor Győri --- (In reply to Andrew Pinski from comment #2) > Sqrt is NOT inlined but rather replaced with __builtin_sqrt which is then > understood as SQRT instruction. This is NOT inlining but rather > understanding builti

[Bug tree-optimization/118297] not vecotrizing some code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118297 Tibor Győri changed: What|Removed |Added URL||https://godbolt.org/z/a5nKv

[Bug target/119079] Intel assembly output should use MOVSXD instead of MOVSX for 32b->64b sign extensions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119079 --- Comment #1 from Tibor Győri --- Created attachment 60630 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60630&action=edit Intel manual page for MOVSX/MOVSXD

[Bug target/119079] New: Intel assembly output should use MOVSXD instead of MOVSX for 32b->64b sign extensions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119079 Bug ID: 119079 Summary: Intel assembly output should use MOVSXD instead of MOVSX for 32b->64b sign extensions Product: gcc Version: 15.0 URL: https://gcc.godbolt.org/