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/95435] bad builtin memcpy performance with znver1/znver2 and 32bit Date: Thu, 30 Jul 2020 08:32:27 +0000 [thread overview] Message-ID: <bug-95435-4-PiaYYX4L44@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95435-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95435 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:dc65aba7a4725d1b464c8c64a5f739ee910e8943 commit r11-2422-gdc65aba7a4725d1b464c8c64a5f739ee910e8943 Author: Martin Liska <mliska@suse.cz> Date: Mon Jun 1 13:21:40 2020 +0200 Tune memcpy and memset for Zen cores. Based on the collected numbers in PR95435, I suggest the following tuning changes: gcc/ChangeLog: PR target/95435 * config/i386/x86-tune-costs.h: Use libcall for large sizes for -m32. Start using libcall from 128+ bytes.
next prev parent reply other threads:[~2020-07-30 8:32 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-30 10:12 [Bug target/95435] New: " jan at jki dot io 2020-05-30 10:12 ` [Bug target/95435] " jan at jki dot io 2020-05-30 10:16 ` jan at jki dot io 2020-05-30 10:18 ` glisse at gcc dot gnu.org 2020-05-30 10:23 ` jan at jki dot io 2020-05-30 16:43 ` amonakov at gcc dot gnu.org 2020-06-01 9:27 ` marxin at gcc dot gnu.org 2020-06-01 9:33 ` marxin at gcc dot gnu.org 2020-06-01 9:48 ` ubizjak at gmail dot com 2020-06-01 10:24 ` amonakov at gcc dot gnu.org 2020-06-01 10:48 ` ubizjak at gmail dot com 2020-06-01 10:58 ` marxin at gcc dot gnu.org 2020-07-30 8:32 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-30 8:39 ` cvs-commit at gcc dot gnu.org 2020-07-30 8:44 ` marxin 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-95435-4-PiaYYX4L44@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).