public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "klaus.doldinger64 at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/66511] [avr] whole-byte shifts not optimized away for uint64_t
Date: Sun, 16 Apr 2023 17:27:33 +0000 [thread overview]
Message-ID: <bug-66511-4-henxkZ0Okf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66511-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66511
Wilhelm M <klaus.doldinger64 at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |klaus.doldinger64@googlemai
| |l.com
--- Comment #5 from Wilhelm M <klaus.doldinger64 at googlemail dot com> ---
(In reply to Roger Sayle from comment #4)
> Created attachment 54871 [details]
> proposed patch
>
> Proposed patch, using a peephole2 in avr-dimode.md to inline calls to
> __lshrdi3 that require only a single instruction or two (due to truncation).
> For truncations to char, this is smaller and faster, and for truncations to
> unsigned short this is the same size, but faster. The drawback is that
> performing this late (in peephole2) doesn't eliminate the stack frame
> prolog/epilog. Thoughts?
Looks good to me.
Many thanks!
prev parent reply other threads:[~2023-04-16 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 14:49 [Bug target/66511] New: " matthijs at stdin dot nl
2015-06-27 17:52 ` [Bug target/66511] " gjl at gcc dot gnu.org
2015-06-27 18:07 ` gjl at gcc dot gnu.org
2015-08-02 11:42 ` matthijs at stdin dot nl
2015-08-13 20:56 ` gjl at gcc dot gnu.org
2023-04-16 12:51 ` roger at nextmovesoftware dot com
2023-04-16 17:27 ` klaus.doldinger64 at googlemail 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-66511-4-henxkZ0Okf@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).