[Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code since r11-6434

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 --- Comment #9 from bartoldeman at users dot sourceforge.net --- I ended up using -mprefer-vector-width=128 as a workaround myself (via __attribute__((target("prefer-vector-width=128", so there is still some AVX vectorization.

[Bug tree-optimization/107647] GCC 12.2.0 may produce FMAs even with -ffp-contract=off

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107647 --- Comment #1 from bartoldeman at users dot sourceforge.net --- According to godbolt it's still producing FMAs on trunk: https://godbolt.org/z/aWh6d1E4E

[Bug tree-optimization/107647] New: GCC 12.2.0 may produce FMAs even with -ffp-contract=off

Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- I stumped upon an example where GCC generates FMA instruction even when FMAs are disabled using -ffp-contract=off

[Bug tree-optimization/107451] [11/12/13 Regression] Segmentation fault with vectorized code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107451 bartoldeman at users dot sourceforge.net changed: What|Removed |Added Attachment #53785|0 |1

[Bug tree-optimization/107451] New: Segmentation fault with vectorized code.

-optimization Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- Created attachment 53785 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53785=edit Test case The following code: double dot(int n, co

[Bug fortran/107294] Missed optimization: multiplying real with complex number in Fortran (only)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107294 bartoldeman at users dot sourceforge.net changed: What|Removed |Added Resolution|FIXED |WONTFIX

[Bug fortran/107294] Missed optimization: multiplying real with complex number in Fortran (only)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107294 bartoldeman at users dot sourceforge.net changed: What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/107294] New: Missed optimization: multiplying real with complex number in Fortran (only)

: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- This code: complex function csmul(a, b) real, value :: a complex, value :: b csmul = a * b end

[Bug tree-optimization/107254] [11/12 Regression] Wrong vectorizer code (Fortran) since r11-1501-gda2b7c7f0a136b4d

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107254 --- Comment #10 from bartoldeman at users dot sourceforge.net --- Thanks for the fix! I can confirm that, when applied to 11.3 (with files renamed from .cc to .c), it fixes the issue, and with it, thousands of test failures in the reference

[Bug tree-optimization/107254] New: Wrong vectorizer code (GCC 11 only, Fortran)

: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- Created attachment 53703 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53703=edit Test case The following code gives the wrong res

[Bug fortran/103023] ICE (Segmentation fault) with !$OMP DECLARE SIMD(func) linear(ref(u))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103023 --- Comment #2 from bartoldeman at users dot sourceforge.net --- Yes this is about the ICE mainly. It was stripped down from this, which HAS uniform. subroutine func(u,f,ndim) !$OMP DECLARE SIMD(func) uniform(ndim) linear(ref(f,u):1

[Bug fortran/103023] New: ICE (Segmentation fault) with !$OMP DECLARE SIMD(func) linear(ref(u))

: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- Created attachment 51717 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51717=edit Test case for cr

[Bug rtl-optimization/101683] Floating point exception for double->unsigned conversion on avx512 only

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101683 --- Comment #6 from bartoldeman at users dot sourceforge.net --- "really not many people care about floating point exceptions". I think more people should :) but this is indeed the context. We found this issue on a supercomput

[Bug target/101683] New: Floating point exception for double->unsigned conversion on avx512 only

ity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- Created attachment 51222 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51222=edit File to rep

[Bug fortran/93734] New: Invalid code generated with -O2 -march=haswell -ftree-vectorize

Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: bartoldeman at users dot sourceforge.net Target Milestone: --- Created attachment 47837 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47837=edit Fortran code that print

[Bug target/52838] New: [x32] missed optimization for pointer return value

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52838 Bug #: 52838 Summary: [x32] missed optimization for pointer return value Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal