public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111354] [7/10/12 regression] The instructions of the DPDK demo program are different and run time increases.
Date: Sat, 09 Sep 2023 05:32:53 +0000	[thread overview]
Message-ID: <bug-111354-4-xRYNcKHzmF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111354-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
First off the performance is difference is die to micro-arch issues with
unaligned stores of 256 bits. 

Also iirc rte_mov128blocks is tuned at copying blocks which are aligned at
least to 32 bytes wide. But you are better asking the dpdk forum why they don't
just use memcpy here.

  reply	other threads:[~2023-09-09  5:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  4:21 [Bug target/111354] New: " d_vampile at 163 dot com
2023-09-09  5:32 ` pinskia at gcc dot gnu.org [this message]
2023-09-09  5:39 ` [Bug target/111354] " pinskia at gcc dot gnu.org
2023-09-09  6:39 ` d_vampile at 163 dot com
2023-09-12 12:12 ` rguenth at gcc dot gnu.org
2023-09-13  9:37 ` crazylht 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-111354-4-xRYNcKHzmF@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).