public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/94804] Failure to elide useless movs in 128-bit addition
Date: Tue, 28 Apr 2020 06:49:39 +0000 [thread overview]
Message-ID: <bug-94804-4-O6Mz4epuv9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94804-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94804
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ra
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
Gcc's register allocation is not well optimized for hard registers at function
boundaries (inlining makes this case not very important), there are several
related bug reports. It would be nice to improve that, but it is likely to get
lower priority than if you can find a similar issue in the middle of a hot
loop.
next prev parent reply other threads:[~2020-04-28 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 16:42 [Bug rtl-optimization/94804] New: " gabravier at gmail dot com
2020-04-27 20:50 ` [Bug rtl-optimization/94804] " gabravier at gmail dot com
2020-04-28 6:49 ` glisse at gcc dot gnu.org [this message]
2020-04-28 7:41 ` rguenth at gcc dot gnu.org
2020-04-28 12:38 ` gabravier at gmail dot com
2020-04-28 17:14 ` glisse at gcc dot gnu.org
2023-01-19 23:17 ` pinskia at gcc dot gnu.org
2023-01-19 23:20 ` [Bug rtl-optimization/94804] Failure to elide useless movs in 128-bit addition with __int128_t arguments pinskia at gcc dot gnu.org
2023-01-19 23:23 ` pinskia 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-94804-4-O6Mz4epuv9@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).