public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109052] Unnecessary reload with -mfpmath=both
Date: Fri, 17 Mar 2023 14:39:48 +0000	[thread overview]
Message-ID: <bug-109052-4-Uz9e2SH18n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109052-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #5)
> (In reply to Vladimir Makarov from comment #4)
> 
> > So I think the current patch is probably an adequate solution.
> 
> Perhaps the compiler should also try to swap input operands to fit the
> combined insn when commutative operands are allowed. This would solve the
> testcase from Comment #2:
> 

Yes.  I am agree.  The base code can be improved further.
Another improvement could be combining secondary memory reload for output.

I'd like to watch what the effect of the current patch would be first.  
Although I tested the patch on many targets as usually for LRA the patch might
result in some troubles on some targets.  But I hope nothing bad will happen.

  parent reply	other threads:[~2023-03-17 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 12:57 [Bug rtl-optimization/109052] New: " ubizjak at gmail dot com
2023-03-07 12:58 ` [Bug rtl-optimization/109052] " ubizjak at gmail dot com
2023-03-07 13:58 ` ubizjak at gmail dot com
2023-03-17 13:07 ` cvs-commit at gcc dot gnu.org
2023-03-17 13:21 ` vmakarov at gcc dot gnu.org
2023-03-17 14:12 ` ubizjak at gmail dot com
2023-03-17 14:39 ` vmakarov at gcc dot gnu.org [this message]
2023-03-17 19:51 ` bergner at gcc dot gnu.org
2023-03-31 15:05 ` cvs-commit at gcc dot gnu.org
2024-01-08  9:10 ` 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-109052-4-Uz9e2SH18n@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).