From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] readkey: shrink table of known escape sequences in size
Date: Mon, 28 Sep 2020 13:51:22 +0200 [thread overview]
Message-ID: <ffe4a9fa-5eec-c9ee-d9d3-44fcd426cc4c@pengutronix.de> (raw)
In-Reply-To: <20200928093102.GA12463@pengutronix.de>
Hello Sascha,
On 9/28/20 11:31 AM, Sascha Hauer wrote:
> On Mon, Sep 14, 2020 at 11:59:48AM +0200, Ahmad Fatoum wrote:
>> Instead of storing pointers to 4-byte strings, we could just store the
>> characters directly in the struct. Can save us up to 18 pointers worth
>> of space. Additionally, the nul byte need not be stored explicitly for
>> 3-byte strings, if we know those are the largest strings we have.
>>
>> The latter likely does not save us any space because of the usual
>> alignment rules, but it will allow us to support sequences one byte
>> bigger in future at no increase in size.
>>
>> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
>> ---
>> lib/readkey.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/lib/readkey.c b/lib/readkey.c
>> index c26e9d51aba9..551296de3eb6 100644
>> --- a/lib/readkey.c
>> +++ b/lib/readkey.c
>> @@ -20,8 +20,10 @@
>> #include <linux/ctype.h>
>> #include <readkey.h>
>>
>> +#define MAX_ESC_LEN 3
>> +
>> struct esc_cmds {
>> - const char *seq;
>> + const char seq[MAX_ESC_LEN];
>
> I would have expected that when this array is initialized with a static
> initializer, the compiler would add a \0 at the end. Apparently this is
> not the case, initializing this 3 byte array with "[6~" is perfectly
> fine for the compiler.
Initializers are padded with zeroes if they are too short.
>> @@ -49,7 +51,7 @@ static const struct esc_cmds esccmds[] = {
>> int read_key(void)
>> {
>> unsigned char c;
>> - unsigned char esc[5];
>> + unsigned char esc[MAX_ESC_LEN + 2];
>> c = getchar();
>>
>> if (c == 27) {
>> @@ -67,7 +69,7 @@ int read_key(void)
>> }
>> esc[i] = 0;
>> for (i = 0; i < ARRAY_SIZE(esccmds); i++){
>> - if (!strcmp(esc, esccmds[i].seq))
>> + if (!strncmp(esc, esccmds[i].seq, MAX_ESC_LEN))
>> return esccmds[i].val;
>
> Anyway, I don't think we should play tricks with dropping string
> termination characters just to squeeze some bytes out of the binary.
I can define #define MAX_ESC_LEN 4 if you prefer that, but I consider
it superfluous.
Cheers,
Ahmad
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2020-09-28 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:59 Ahmad Fatoum
2020-09-28 9:31 ` Sascha Hauer
2020-09-28 11:51 ` Ahmad Fatoum [this message]
2020-09-28 11:58 ` Sascha Hauer
2020-09-28 12:40 ` Ahmad Fatoum
2020-09-28 12:39 Ahmad Fatoum
2020-09-30 7:31 ` Sascha Hauer
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=ffe4a9fa-5eec-c9ee-d9d3-44fcd426cc4c@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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