From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: thomas@t-8ch.de, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 02/11] tools/nolibc: add new crt.h with _start_c
Date: Thu, 13 Jul 2023 08:34:18 +0200 [thread overview]
Message-ID: <ZK+a6rEJIUjCnNsZ@1wt.eu> (raw)
In-Reply-To: <20230713061227.43222-1-falcon@tinylab.org>
Hi Zhangjin,
I haven't reviewed the rest yet but regarding this point:
On Thu, Jul 13, 2023 at 02:12:27PM +0800, Zhangjin Wu wrote:
> > > + /* find auxv */
> > > + i = 0;
> > > + while (envp[i])
> > > + i++;
> > > + _auxv = (void *)(envp + i + 1);
> >
> > Could be simplified a bit:
> >
> > _auxv = (void *) envp;
> > while (_auxv)
> > _auxv++;
> >
>
> Yeah, it is better, but needs a little change.
>
> _auxv = (void *) envp;
> while (*_auxv)
> _auxv++;
> _auxv++;
Or just:
_auxv = (void*)environ;
while (*_auxv++)
;
or:
for (_auxv = (void*)environ; *_auxv++; )
;
Please also have a look at the output code, because at low optimization
levels, compilers sometimes produce a better code with a local variable
than with a global variable in a loop. Thus I wouldn't be that much
surprised if at -O0 or -O1 you'd see slightly more compact code using:
/* find envp */
environ = argv + argc + 1;
/* find auxv */
for (auxv = environ; *auxv++)
;
_auxv = auxv;
than:
/* find envp */
envp = argv + argc + 1;
environ = envp;
/* find auxv */
for (_auxv = environ; *_auxv++)
;
Since it's going to become generic code, it's worth running a few tests
to see how to best polish it.
Thanks,
Willy
next prev parent reply other threads:[~2023-07-13 6:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 9:15 [PATCH v3 00/11] tools/nolibc: shrink arch support Zhangjin Wu
2023-07-12 9:16 ` [PATCH v3 01/11] tools/nolibc: remove the old sys_stat support Zhangjin Wu
2023-07-15 8:59 ` Willy Tarreau
2023-07-15 10:39 ` Zhangjin Wu
2023-07-15 11:45 ` Willy Tarreau
2023-07-12 9:17 ` [PATCH v3 02/11] tools/nolibc: add new crt.h with _start_c Zhangjin Wu
2023-07-12 20:39 ` Thomas Weißschuh
2023-07-13 6:12 ` Zhangjin Wu
2023-07-13 6:23 ` Zhangjin Wu
2023-07-13 6:24 ` Thomas Weißschuh
2023-07-13 6:34 ` Willy Tarreau [this message]
2023-07-14 5:58 ` Zhangjin Wu
2023-07-14 6:34 ` Thomas Weißschuh
2023-07-14 9:47 ` Zhangjin Wu
2023-07-15 7:24 ` Thomas Weißschuh
2023-07-15 9:23 ` Zhangjin Wu
2023-07-15 9:57 ` Willy Tarreau
2023-07-12 9:18 ` [PATCH v3 03/11] tools/nolibc: arm: shrink _start " Zhangjin Wu
2023-07-12 9:19 ` [PATCH v3 04/11] tools/nolibc: aarch64: " Zhangjin Wu
2023-07-12 9:20 ` [PATCH v3 05/11] tools/nolibc: i386: " Zhangjin Wu
2023-07-12 9:22 ` [PATCH v3 06/11] tools/nolibc: x86_64: " Zhangjin Wu
2023-07-12 9:23 ` [PATCH v3 07/11] tools/nolibc: mips: " Zhangjin Wu
2023-07-12 9:24 ` [PATCH v3 08/11] tools/nolibc: loongarch: " Zhangjin Wu
2023-07-12 9:25 ` [PATCH v3 09/11] tools/nolibc: riscv: " Zhangjin Wu
2023-07-12 9:26 ` [PATCH v3 10/11] tools/nolibc: s390: " Zhangjin Wu
2023-07-12 9:27 ` [PATCH v3 11/11] tools/nolibc: arch-*.h: add missing space after ',' Zhangjin Wu
2023-07-15 10:01 ` [PATCH v3 00/11] tools/nolibc: shrink arch support Willy Tarreau
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=ZK+a6rEJIUjCnNsZ@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.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