public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/103550] 2 more instructions generated by gcc than clang
Date: Sat, 04 Dec 2021 07:07:32 +0000 [thread overview]
Message-ID: <bug-103550-4-lXRFbWQovX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103550-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103550
--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #2)
> Looks like it is a register allocation/scheduling issue. The extra
> instructions are mov.
yeah. I feel gcc generally has issues with register allocations.
next prev parent reply other threads:[~2021-12-04 7:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 6:56 [Bug rtl-optimization/103550] New: " unlvsur at live dot com
2021-12-04 6:59 ` [Bug rtl-optimization/103550] " pinskia at gcc dot gnu.org
2021-12-04 7:04 ` pinskia at gcc dot gnu.org
2021-12-04 7:07 ` unlvsur at live dot com [this message]
2021-12-04 7:08 ` unlvsur at live dot com
2021-12-04 7:15 ` pinskia at gcc dot gnu.org
2021-12-04 7:22 ` unlvsur at live dot com
2021-12-04 7:32 ` unlvsur at live dot com
2021-12-04 11:30 ` roger at nextmovesoftware dot com
2021-12-04 11:52 ` roger at nextmovesoftware dot com
2021-12-04 13:56 ` unlvsur at live dot com
2022-10-06 6:47 ` 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-103550-4-lXRFbWQovX@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).