public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105504] Fails to break dependency for vcvtss2sd xmm, xmm, mem
Date: Sat, 07 May 2022 03:16:06 +0000	[thread overview]
Message-ID: <bug-105504-4-8AXUG4BLxK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105504-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105504

--- Comment #2 from Hongtao.liu <crazylht at gmail dot com> ---
After set remove_partial_avx_dependency to true for register alternative, we
get

       vxorps  %xmm3, %xmm3, %xmm3
        vmovsd  .LC16(%rip), %xmm6
        vmovsd  .LC14(%rip), %xmm5
        vcvtss2sd       %xmm0, %xmm3, %xmm0
        vmulsd  .LC12(%rip), %xmm0, %xmm1
        vroundsd        $9, %xmm1, %xmm3, %xmm2
        vcvttsd2siq     %xmm2, %rax
        vsubsd  %xmm2, %xmm1, %xmm1
        vfmadd231sd     .LC13(%rip), %xmm0, %xmm1
        vfmadd213sd     .LC17(%rip), %xmm1, %xmm6
        vmovsd  .LC18(%rip), %xmm0
        vfmadd213sd     .LC19(%rip), %xmm1, %xmm0
        vfmadd213sd     .LC15(%rip), %xmm1, %xmm5
        movq    %rax, %rdx
        sarq    $4, %rax
        vmulsd  %xmm1, %xmm1, %xmm4
        addq    $1023, %rax
        andl    $15, %edx
        salq    $52, %rax
        vmovq   %rax, %xmm7
        vmulsd  tb.1(,%rdx,8), %xmm7, %xmm2
        vfmadd132sd     %xmm4, %xmm6, %xmm0
        vmulsd  %xmm2, %xmm1, %xmm1
        vfmadd132sd     %xmm4, %xmm5, %xmm0
        vfmadd132sd     %xmm1, %xmm2, %xmm0
        vcvtsd2ss       %xmm0, %xmm3, %xmm0

Also  
>Also there's a potentially related issue that GCC copies the initial xmm0 value >to eax via stack in the beginning of the function:

This issue disappears(should still be latent after fix).

  parent reply	other threads:[~2022-05-07  3:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  9:12 [Bug target/105504] New: " amonakov at gcc dot gnu.org
2022-05-07  3:02 ` [Bug target/105504] " crazylht at gmail dot com
2022-05-07  3:16 ` crazylht at gmail dot com [this message]
2022-05-07  3:36 ` crazylht at gmail dot com
2022-05-07  4:04 ` crazylht at gmail dot com
2022-05-07  8:28 ` amonakov at gcc dot gnu.org
2022-06-08  3:24 ` cvs-commit at gcc dot gnu.org
2023-08-05 15:05 ` egallager at gcc dot gnu.org
2023-08-07  1:55 ` crazylht at gmail dot com
2023-08-12 13:50 ` egallager at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105504-4-8AXUG4BLxK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).