public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111657] Memory copy with structure assignment from named address space should be improved
Date: Mon, 02 Oct 2023 09:25:59 +0000	[thread overview]
Message-ID: <bug-111657-4-URjUB8I3e5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111657-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
I have tried to compile with -mtune=nocona that has:

static stringop_algs nocona_memcpy[2] = {
  {libcall, {{12, loop_1_byte, false}, {-1, rep_prefix_4_byte, false}}},
  {libcall, {{32, loop, false}, {20000, rep_prefix_8_byte, false},
             {100000, unrolled_loop, false}, {-1, libcall, false}}}};

and compiler produces code as expected in both cases (use unrolled_loop when
rep movsq is unavailable):

foo:
        movq    %fs:0, %rdx
        leaq    t@tpoff(%rdx), %rsi
        movl    $30, %ecx
        rep movsq
        ret

bar:
        xorl    %edx, %edx
.L4:
        movl    %edx, %eax
        movq    %gs:s(%rax), %r9
        movq    %gs:s+8(%rax), %r8
        movq    %gs:s+16(%rax), %rsi
        movq    %gs:s+24(%rax), %rcx
        movq    %r9, (%rdi,%rax)
        movq    %r8, 8(%rdi,%rax)
        movq    %rsi, 16(%rdi,%rax)
        movq    %rcx, 24(%rdi,%rax)
        addl    $32, %edx
        cmpl    $224, %edx
        jb      .L4
        addq    %rdx, %rdi
        movq    %gs:s(%rdx), %rax
        movq    %rax, (%rdi)
        movq    %gs:s+8(%rdx), %rax
        movq    %rax, 8(%rdi)
        ret

  parent reply	other threads:[~2023-10-02  9:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 21:41 [Bug middle-end/111657] New: Memory copy with structure assignment from named address space is not working ubizjak at gmail dot com
2023-10-01 21:57 ` [Bug middle-end/111657] " ubizjak at gmail dot com
2023-10-01 22:26 ` pinskia at gcc dot gnu.org
2023-10-01 22:31 ` [Bug target/111657] Memory copy with structure assignment from named address space should be improved pinskia at gcc dot gnu.org
2023-10-02  9:21 ` ubizjak at gmail dot com
2023-10-02  9:25 ` ubizjak at gmail dot com [this message]
2023-10-05 15:43 ` cvs-commit at gcc dot gnu.org
2023-10-05 15:46 ` ubizjak at gmail dot com
2023-11-17 12:07 ` jakub at gcc dot gnu.org
2023-11-17 13:39 ` ubizjak at gmail dot com

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-111657-4-URjUB8I3e5@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).