public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/58110] New: Useless GPR push and pop when only xmm registers are used.
Date: Fri, 09 Aug 2013 12:38:00 -0000	[thread overview]
Message-ID: <bug-58110-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58110

            Bug ID: 58110
           Summary: Useless GPR push and pop when only xmm registers are
                    used.
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: neleai at seznam dot cz

Hi,attached code generates extra push/pop rbx pair while there is no gpr
register assigned in segment between them.
This was generated by head xgcc -O3. A gcc-4.7 has similar issues with attached
program.

  pushq   %rbx
        .cfi_def_cfa_offset 16
        .cfi_offset 3, -16
        movdqu  (%rsi), %xmm15
        movdqu  -16(%rsi,%rdx), %xmm14
        movdqu  16(%rsi), %xmm13
        movdqu  -32(%rsi,%rdx), %xmm12
        movdqu  32(%rsi), %xmm11
        movdqu  -48(%rsi,%rdx), %xmm10
        movdqu  48(%rsi), %xmm9
        movdqu  -64(%rsi,%rdx), %xmm8
        movdqu  64(%rsi), %xmm7
        movdqu  -80(%rsi,%rdx), %xmm6
        movdqu  80(%rsi), %xmm5
        movdqu  -96(%rsi,%rdx), %xmm4
        movdqu  96(%rsi), %xmm3
        movdqu  -112(%rsi,%rdx), %xmm2
        movdqu  112(%rsi), %xmm1
        movdqu  -128(%rsi,%rdx), %xmm0
        movdqu  %xmm15, (%rdi)
        movdqu  %xmm14, -16(%rdi,%rdx)
        movdqu  %xmm13, 16(%rdi)
        movdqu  %xmm12, -32(%rdi,%rdx)
        movdqu  %xmm11, 32(%rdi)
        movdqu  %xmm10, -48(%rdi,%rdx)
        movdqu  %xmm9, 48(%rdi)
        movdqu  %xmm8, -64(%rdi,%rdx)
        movdqu  %xmm7, 64(%rdi)
        movdqu  %xmm6, -80(%rdi,%rdx)
        movdqu  %xmm5, 80(%rdi)
        movdqu  %xmm4, -96(%rdi,%rdx)
        movdqu  %xmm3, 96(%rdi)
        movdqu  %xmm2, -112(%rdi,%rdx)
        movdqu  %xmm1, 112(%rdi)
        movdqu  %xmm0, -128(%rdi,%rdx)
        popq    %rbx


             reply	other threads:[~2013-08-09 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 12:38 neleai at seznam dot cz [this message]
2013-08-09 12:39 ` [Bug target/58110] " neleai at seznam dot cz
2013-08-09 13:52 ` hubicka at gcc dot gnu.org
2013-08-09 19:02 ` vmakarov at redhat dot com
2021-09-12  2:39 ` pinskia 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-58110-4@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).