public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Thu, 05 Oct 2023 15:43:21 +0000 [thread overview] Message-ID: <bug-111657-4-lw2Dd3lRVe@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 #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:c6bff80d786919f2f64e8a9f3179d6d36888bdb3 commit r14-4418-gc6bff80d786919f2f64e8a9f3179d6d36888bdb3 Author: Uros Bizjak <ubizjak@gmail.com> Date: Thu Oct 5 17:40:37 2023 +0200 i386: Improve memory copy from named address space [PR111657] The stringop strategy selection algorithm falls back to a libcall strategy when it exhausts its pool of available strategies. The memory area copy function (memcpy) is not availabe from the system library for non-default address spaces, so the compiler emits the most trivial byte-at-a-time copy loop instead. The compiler should instead emit an optimized copy loop as a fallback for non-default address spaces. PR target/111657 gcc/ChangeLog: * config/i386/i386-expand.cc (alg_usable_p): Reject libcall strategy for non-default address spaces. (decide_alg): Use loop strategy as a fallback strategy for non-default address spaces. gcc/testsuite/ChangeLog: * gcc.target/i386/pr111657.c: New test.
next prev parent reply other threads:[~2023-10-05 15:43 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 2023-10-05 15:43 ` cvs-commit at gcc dot gnu.org [this message] 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-lw2Dd3lRVe@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: linkBe 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).