public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95021] [10/11 Regression] Bogus -Wclobbered warning
Date: Tue, 12 May 2020 13:34:50 +0000	[thread overview]
Message-ID: <bug-95021-4-W8KvhG63WX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95021-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
STV generates:

        8d b6 00 00 00 00       lea    0x0(%esi),%esi
        a1 00 00 00 00          mov    0x0,%eax R_386_32        target_p
        83 ec 08                sub    $0x8,%esp
        f3 0f 7e 00             movq   (%eax),%xmm0
        a1 00 00 00 00          mov    0x0,%eax R_386_32        c
        66 0f 6f c8             movdqa %xmm0,%xmm1
        66 0f 7e 44 24 10       movd   %xmm0,0x10(%esp)
        66 0f 73 d1 20          psrlq  $0x20,%xmm1
        66 0f d6 00             movq   %xmm0,(%eax)
        66 0f 7e 4c 24 14       movd   %xmm1,0x14(%esp)
        ff 74 24 14             pushl  0x14(%esp)
        ff 74 24 14             pushl  0x14(%esp)
        e8 fc ff ff ff          call   <d+0x53> R_386_PC32      e

instead of

        8d b6 00 00 00 00       lea    0x0(%esi),%esi
        a1 00 00 00 00          mov    0x0,%eax R_386_32        target_p
        8b 0d 00 00 00 00       mov    0x0,%ecx R_386_32        c
        83 ec 08                sub    $0x8,%esp
        8b 50 04                mov    0x4(%eax),%edx
        8b 00                   mov    (%eax),%eax
        89 51 04                mov    %edx,0x4(%ecx)
        89 01                   mov    %eax,(%ecx)
        52                      push   %edx
        50                      push   %eax
        e8 fc ff ff ff          call   <d+0x3b> R_386_PC32      e

It is hard to tell if vector is faster.

  parent reply	other threads:[~2020-05-12 13:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 16:14 [Bug middle-end/95021] New: " hjl.tools at gmail dot com
2020-05-09 19:19 ` [Bug middle-end/95021] " hjl.tools at gmail dot com
2020-05-11  1:26 ` hjl.tools at gmail dot com
2020-05-11  6:44 ` rguenth at gcc dot gnu.org
2020-05-12 13:08 ` hjl.tools at gmail dot com
2020-05-12 13:34 ` hjl.tools at gmail dot com [this message]
2020-05-12 13:50 ` rguenther at suse dot de
2020-05-12 20:08 ` hjl.tools at gmail dot com
2020-05-13 13:28 ` hjl.tools at gmail dot com
2020-05-17 17:13 ` cvs-commit at gcc dot gnu.org
2020-05-17 17:14 ` hjl.tools at gmail dot com
2020-05-18 19:01 ` ro at gcc dot gnu.org
2020-07-23  6:51 ` rguenth at gcc dot gnu.org
2021-01-14  8:43 ` [Bug middle-end/95021] [10 " rguenth at gcc dot gnu.org
2021-01-14  9:27 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-14 10:12 ` rguenth at gcc dot gnu.org
2021-01-14 11:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-01-14 12:19 ` rguenth at gcc dot gnu.org
2021-01-14 15:05 ` cvs-commit at gcc dot gnu.org
2021-01-14 15:46 ` hjl.tools at gmail dot com
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07  8:50 ` rguenth 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-95021-4-W8KvhG63WX@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).