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 middle-end/102294] structure assignment slower than memberwise initialization
Date: Mon, 13 Sep 2021 02:25:29 +0000	[thread overview]
Message-ID: <bug-102294-4-ZT2teJZ5hb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102294-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is literally just measuring memset times of a small structure.

-mtune=intel changes the timings too.
Doing -mstringop-strategy=libcall also changes the timing to the point where
they are about the same as clang.

So this is a target issue and not a middle-end.

You need to do timings on many more processors to have the -mtune=generic
changed.

  parent reply	other threads:[~2021-09-13  2:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 21:59 [Bug c/102294] New: " bart.vanassche at gmail dot com
2021-09-12 22:17 ` [Bug middle-end/102294] " pinskia at gcc dot gnu.org
2021-09-13  1:41 ` bart.vanassche at gmail dot com
2021-09-13  1:43 ` bart.vanassche at gmail dot com
2021-09-13  1:59 ` pinskia at gcc dot gnu.org
2021-09-13  2:16 ` bart.vanassche at gmail dot com
2021-09-13  2:25 ` pinskia at gcc dot gnu.org [this message]
2021-09-13  2:57 ` [Bug middle-end/102294] memset expansion is sometimes slow for small sizes bart.vanassche at gmail dot com
2021-09-13  3:06 ` crazylht at gmail dot com
2021-09-13  3:21 ` bart.vanassche at gmail dot com
2021-09-13  3:28 ` crazylht at gmail dot com
2021-09-13  3:40 ` [Bug target/102294] " pinskia at gcc dot gnu.org
2021-09-13 13:37 ` hjl.tools at gmail dot com
2021-09-14  2:04 ` bart.vanassche 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-102294-4-ZT2teJZ5hb@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).