[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-25 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #13 from Hongtao.liu --- ;; Function fn (fn, funcdef_no=5484, decl_uid=32317, cgraph_uid=5485, symbol_order=5484) int fn (const int * px, const int * py, const int * pz, const int * pw, const int * pa, const int * pb, const int *

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #12 from Hongtao.liu --- (In reply to Hongtao.liu from comment #11) > (In reply to Andrew Pinski from comment #10) > > (In reply to Andrew Pinski from comment #9) > > > (In reply to Hongtao.liu from comment #8) > > > > Do we have IR

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #11 from Hongtao.liu --- (In reply to Andrew Pinski from comment #10) > (In reply to Andrew Pinski from comment #9) > > (In reply to Hongtao.liu from comment #8) > > > Do we have IR for unsigned/signed saturation in gimple level? > >

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #10 from Andrew Pinski --- (In reply to Andrew Pinski from comment #9) > (In reply to Hongtao.liu from comment #8) > > Do we have IR for unsigned/signed saturation in gimple level? > > Not yet. I was just looking for that today due

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #9 from Andrew Pinski --- (In reply to Hongtao.liu from comment #8) > Do we have IR for unsigned/signed saturation in gimple level? Not yet. I was just looking for that today due because of PR 51492.

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #8 from Hongtao.liu --- (In reply to Hongtao.liu from comment #7) > (In reply to Andrew Pinski from comment #5) > > clang can now produce: > > mov eax, dword ptr [esp + 16] > > mov ecx, dword ptr [esp + 28] >

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread crazylht at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #7 from Hongtao.liu --- (In reply to Andrew Pinski from comment #5) > clang can now produce: > mov eax, dword ptr [esp + 16] > mov ecx, dword ptr [esp + 28] > vmovdqu xmm0, xmmword ptr [ecx + 32] >

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-24 Thread kobalicek.petr at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #6 from Petr --- Yes, the code is not really doing anything useful, I only wrote it to demonstrate the spills problem. Clang actually outsmarted me by removing half of the code :) I think this issue can be closed, I cannot repro

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2021-08-13 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 Andrew Pinski changed: What|Removed |Added Component|rtl-optimization|target --- Comment #5 from Andrew

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2016-08-18 Thread kobalicek.petr at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 --- Comment #2 from Petr --- With '-mtune=intel' the push/pop sequence is gone, but YMM register management remains the same - 24 memory accesses more than clang.

[Bug target/77287] Much worse code generated compared to clang (stack alignment and spills)

2016-08-18 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77287 Andrew Pinski changed: What|Removed |Added Component|c++ |target --- Comment #1 from Andrew