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/110024] [Bug] 5% performance drop on important benchmark after r260951.
Date: Mon, 29 May 2023 15:19:20 +0000	[thread overview]
Message-ID: <bug-110024-4-wf4fI2V8Vj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110024-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from d_vampile <d_vampile at 163 dot com> ---
(In reply to Andrew Pinski from comment #2)
> Which core is showing the difference here?
> Because some cores I know of, loading/storing using the FP registers is
> actually one cycle slower than using GPRs.
Yes, you're right; This submission is due to my careless post wrong assembly
code location; The performance is better when the X0 register is used before
the modification. The question, however, is why this modification causes the
register to select D0 and performance degradation. In addition, I will continue
to follow up in the new submission, look forward to your reply.

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

      parent reply	other threads:[~2023-05-29 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 14:42 [Bug target/110024] New: " d_vampile at 163 dot com
2023-05-29 14:46 ` [Bug target/110024] " d_vampile at 163 dot com
2023-05-29 14:48 ` pinskia at gcc dot gnu.org
2023-05-29 15:09 ` d_vampile at 163 dot com
2023-05-29 15:19 ` d_vampile at 163 dot com [this message]

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-110024-4-wf4fI2V8Vj@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).