From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: VJHC code changes and whitespace removals
Date: Thu, 16 Mar 2017 08:55:38 -0400 [thread overview]
Message-ID: <f0d648de-659c-350e-e35a-adeb810a3329@jodybruchon.com> (raw)
I'm pushing a change to elkscmd/ktcp/vjhc.* that moves various
encode/decode functions specified as macros in vjhc.h into vjhc.c as
functions. This will slightly reduce VJHC performance due to function
call overhead but it cuts code size in vjhc.o by 21%, saving about 2.6K
in the final binary:
$ size86 vjhc.o*
text data bss dec hex filename
12576 14 34 12624 3150 vjhc.o
9913 14 34 9961 26e9 vjhc.o.new
$ size86 ktcp*
text data bss dec hex filename
33296 916 8176 42388 a594 ktcp.old
30640 916 8176 39732 9b34 ktcp.new
If anyone uses SLIP with VJHC, please test this change to make sure it
didn't break anything.
I've also used sed to kill off trailing whitespace in the entire
elks/elkscmd code base. Let me know if this messed anything up; my tests
after doing this were OK.
-Jody
reply other threads:[~2017-03-16 12:55 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=f0d648de-659c-350e-e35a-adeb810a3329@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.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).