public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d_vampile at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111332] Using GCC7.3.0 and GCC10.3.0 to compile the same test case, assembler file instructions are different and performance fallback is obvious.
Date: Fri, 08 Sep 2023 02:34:05 +0000	[thread overview]
Message-ID: <bug-111332-4-WFFuUITos7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111332-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from d_vampile <d_vampile at 163 dot com> ---
According to the analysis, the following two prs may cause the preceding
problems:
PR1:https://github.com/gcc-mirror/gcc/commit/dd9b529f08c3c6064c37234922d298336d78caf7
PR2:https://github.com/gcc-mirror/gcc/commit/e7bf9583fa2a16e9edd5d5347407ad8acc8f9794

I revert PR1 on gcc10.3.0 and found that the assembly instructions changed to
vmovups and vmovups.

And revert PR2, the order of assembly instructions can be consistent with that
of instructions generated during gcc7.3.0 compilation. However, the effects  of
these two PRs and the potential risks of code rollback are still noclear.

  parent reply	other threads:[~2023-09-08  2:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  1:49 [Bug target/111332] New: " d_vampile at 163 dot com
2023-09-08  1:54 ` [Bug target/111332] " d_vampile at 163 dot com
2023-09-08  1:58 ` d_vampile at 163 dot com
2023-09-08  2:11 ` pinskia at gcc dot gnu.org
2023-09-08  2:16 ` pinskia at gcc dot gnu.org
2023-09-08  2:34 ` d_vampile at 163 dot com [this message]
2023-09-08  2:38 ` d_vampile at 163 dot com
2023-09-08  2:40 ` d_vampile at 163 dot com
2023-09-08  4:00 ` pinskia at gcc dot gnu.org
2023-09-08  4:09 ` d_vampile at 163 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-111332-4-WFFuUITos7@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).