subject:"\[Bug tree\-optimization\/88540\] Issues with vectorization of min\/max operations"

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-07-31 Thread rguenth at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 Richard Biener changed: What|Removed |Added Target Milestone|--- |14.0

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-07-31 Thread rguenth at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-07-21 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 --- Comment #8 from CVS Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:9f8f37f5490076b10436993fb90d18092a960922 commit r14-2699-g9f8f37f5490076b10436993fb90d18092a960922 Author: Richard Biener Date:

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-07-12 Thread crazylht at gmail dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 --- Comment #7 from Hongtao.liu --- (In reply to Hongtao.liu from comment #6) > Note, x86 MINSS/MAXSS is not IEEE-conformant minimum and maximum operations, > it always return the second operand when there's NAN, but for > fmin/fmax_optab it shou

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-07-12 Thread crazylht at gmail dot com via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 Hongtao.liu changed: What|Removed |Added CC||crazylht at gmail dot com --- Comment #6 f

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2023-04-09 Thread pinskia at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 --- Comment #5 from Andrew Pinski --- > Also minmax_replacement in phi-opt could make > use of the FMIN/FMAX IFNs when HONOR_NANS || HONOR_SIGNED_ZEROS > and the direct IFN is available. You should just need to teach match.pd rather than minmax_

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2020-05-07 Thread rguenth at gcc dot gnu.org

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 Richard Biener changed: What|Removed |Added Blocks||94864 Status|NEW

[Bug tree-optimization/88540] Issues with vectorization of min/max operations

2018-12-19 Thread bugzi...@poradnik-webmastera.com

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88540 --- Comment #3 from Daniel Fruzynski --- Looks that AARCH64 is also affected. This is output from gcc 8.2 for SIZE=2: [asm] test(double*, double*, double*): ldp d1, d0, [x0] ldp d3, d2, [x1] fcmpe d1, d3