public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100348] RISC-V extra pointer adjustments for memcpy() from glibc
Date: Fri, 30 Apr 2021 19:01:02 +0000	[thread overview]
Message-ID: <bug-100348-4-2d6Cx6AJVv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100348-4@http.gcc.gnu.org/bugzilla/>

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

Jim Wilson <wilson at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wilson at gcc dot gnu.org

--- Comment #1 from Jim Wilson <wilson at gcc dot gnu.org> ---
Most glibc targets already have an assembly language memcpy.S implementation. 
RISC-V should also.  This is likely the most effective solution to the problem. 
 We should fix the optimizer problem if possible of course.  It is just that
the glibc solution is likely easier than the gcc solution.

  reply	other threads:[~2021-04-30 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 23:40 [Bug target/100348] New: " brian.grayson at sifive dot com
2021-04-30 19:01 ` wilson at gcc dot gnu.org [this message]
2021-04-30 19:01 ` [Bug target/100348] " wilson 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-100348-4-2d6Cx6AJVv@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).