From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Brandon Casey" <casey@nrlssc.navy.mil>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <junkio@cox.net>,
davidk@lysator.liu.se, "Andreas Ericsson" <ae@op5.se>
Subject: Re: [PATCH] dir.c: avoid c99 array initialization
Date: Thu, 28 Aug 2008 22:01:53 +0200 [thread overview]
Message-ID: <81b0412b0808281301m29830c20l3e16432ea8aef45d@mail.gmail.com> (raw)
In-Reply-To: <G-ipWASixyGW7nvO1KquifehvBB7FNKwjPtIB0ukyEJ1Si1CJWM34w@cipher.nrlssc.navy.mil>
2008/8/19 Brandon Casey <casey@nrlssc.navy.mil>:
> static int simple_length(const char *match)
> {
> - const char special[256] = {
> - [0] = 1, ['?'] = 1,
> - ['\\'] = 1, ['*'] = 1,
> - ['['] = 1
> - };
> + char special[256] = { 1, };
> int len = -1;
>
> + special['?'] = 1;
> + special['\\'] = 1;
> + special['*'] = 1;
> + special['['] = 1;
For just these 5 values it is likely more effective to just use
a conditional statement (less stack requested, less likely
some stupid compiler tries to optimize it wrongly).
And just as readable.
diff --git a/dir.c b/dir.c
index 92452eb..1cf5985 100644
--- a/dir.c
+++ b/dir.c
@@ -680,17 +680,12 @@ static int cmp_name(const void *p1, const void *p2)
*/
static int simple_length(const char *match)
{
- const char special[256] = {
- [0] = 1, ['?'] = 1,
- ['\\'] = 1, ['*'] = 1,
- ['['] = 1
- };
int len = -1;
for (;;) {
unsigned char c = *match++;
len++;
- if (special[c])
+ if (!c || '?' == c || '\\' == c || '*' == c || '[' == c)
return len;
}
}
next prev parent reply other threads:[~2008-08-28 20:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 23:39 [FYI] How I compile on SunOS 5.7 with the SUNWspro compiler and ksh Brandon Casey
2008-08-18 23:55 ` [PATCH] Makefile: configuration for SunOS 5.7 Brandon Casey
2008-08-18 23:57 ` [PATCH] dir.c: avoid c99 array initialization Brandon Casey
2008-08-28 15:32 ` David Kågedal
2008-08-28 15:41 ` Andreas Ericsson
2008-08-28 16:45 ` Brandon Casey
2008-08-28 18:50 ` Junio C Hamano
2008-08-28 21:01 ` Brandon Casey
2008-08-28 21:12 ` Alex Riesen
2008-08-28 21:45 ` Brandon Casey
2008-08-28 20:01 ` Alex Riesen [this message]
2008-08-28 20:16 ` Shawn O. Pearce
2008-08-28 20:21 ` Junio C Hamano
2008-08-28 22:47 ` [PATCH v2] dir.c: Avoid " Brandon Casey
2008-08-28 22:56 ` Alex Riesen
2008-08-28 23:03 ` Brandon Casey
2008-08-28 20:27 ` [PATCH] dir.c: avoid " Alex Riesen
2008-08-29 11:08 ` Johannes Schindelin
2008-08-19 0:08 ` [PATCH FYI] reset,cat-file: remove const declaration from array Brandon Casey
2008-08-19 0:11 ` [PATCH FYI] test-lib.sh: work around ksh's trap shortcomings Brandon Casey
2008-08-19 0:13 ` [PATCH FYI] t1002-read-tree-m-u-2way.sh: use 'git diff -U0' rather than 'diff -U0' Brandon Casey
2008-08-19 0:18 ` [PATCH FYI] Work around sed issues Brandon Casey
2008-08-19 0:20 ` [PATCH FYI] t9301-fast-export.sh: don't unset config variable while we're skipping test 4 Brandon Casey
2008-08-19 0:20 ` [FYI] How I compile on SunOS 5.7 with the SUNWspro compiler and ksh Jeff King
2008-08-19 0:47 ` Brandon Casey
2008-08-19 2:01 ` Jeff King
2008-08-19 0:22 ` [PATCH FYI] t9700/test.pl: backwards compatibility improvements Brandon Casey
2008-09-15 11:54 ` Tom G. Christensen
2008-09-15 16:20 ` Brandon Casey
2008-09-15 16:32 ` Brandon Casey
2008-09-15 16:20 ` [PATCH 1/3] t9700/test.pl: no longer requires File::Basename Brandon Casey
2008-09-15 16:23 ` [PATCH 2/3] t9700/test.pl: avoid bareword 'STDERR' in 3-argument open() Brandon Casey
2008-09-15 16:25 ` [PATCH 3/3] t9700/test.pl: remove File::Temp requirement Brandon Casey
2008-09-15 18:27 ` Tom G. Christensen
2008-08-19 6:13 ` [FYI] How I compile on SunOS 5.7 with the SUNWspro compiler and ksh Alex Riesen
2008-08-19 15:42 ` Brandon Casey
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=81b0412b0808281301m29830c20l3e16432ea8aef45d@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=ae@op5.se \
--cc=casey@nrlssc.navy.mil \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 NNTP newsgroup(s).