From: Kaushik Phatak <Kaushik.Phatak@kpit.com>
To: "'gcc-patches@gcc.gnu.org'" <gcc-patches@gcc.gnu.org>
Cc: "nick clifton (nickc@redhat.com)" <nickc@redhat.com>
Subject: RE: [PING PATCH: RL78] Optimize libgcc routines using clrw and clrb
Date: Tue, 23 Feb 2016 07:41:00 -0000 [thread overview]
Message-ID: <SG2PR03MB139180CAD922FF22569C4E0CFCA40@SG2PR03MB1391.apcprd03.prod.outlook.com> (raw)
Hi Nick,
Please let me know if you have had a chance to look at the following patch,
https://gcc.gnu.org/ml/gcc-patches/2016-02/msg00415.html
Best Regards,
Kaushik
-----Original Message-----
From: Kaushik Phatak
Sent: Friday, February 05, 2016 6:26 PM
To: 'gcc-patches@gcc.gnu.org' <gcc-patches@gcc.gnu.org>
Cc: nick clifton (nickc@redhat.com) <nickc@redhat.com>
Subject: [PATCH: RL78] Optimize libgcc routines using clrw and clrb
Hi,
Please find below a simple patch which optimizes the loading of immediate value by using the clrw or clrb instruction in case a 0x00 is being loaded into the register.
The patch replaces movw/mov instruction with the smaller clrw/clrb instruction.
The clrw and clrb generates only 1 byte of opcode as compared to 3 or 2 bytes for movw and mov.
There is a total of about 94 bytes code size improvement with this patch in these libgcc routines.
reply other threads:[~2016-02-23 7:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=SG2PR03MB139180CAD922FF22569C4E0CFCA40@SG2PR03MB1391.apcprd03.prod.outlook.com \
--to=kaushik.phatak@kpit.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
/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).