Linux kbuild/kconfig development
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] cc-can-link.sh: check for linking capability in a more robust way
Date: Tue, 6 Jul 2021 00:22:08 +0300	[thread overview]
Message-ID: <YON4AKdi9ISn3gvk@localhost.localdomain> (raw)
In-Reply-To: <CAK7LNASnUV7i17QKAULLVmbS4=fBE1Lcm=8uH6rfwmT-CAkY2w@mail.gmail.com>

On Tue, Jul 06, 2021 at 01:33:45AM +0900, Masahiro Yamada wrote:
> On Sat, Jul 3, 2021 at 8:21 PM Alexey Dobriyan <adobriyan@gmail.com> wrote:
> >
> > Compiling "printf("");" doesn't necessarily check for linking capability
> > as printf can be optimised for constants strings even at -O0:
> >
> >         0000000000401106 <main>:
> >           401106:       push   rbp
> >           401107:       mov    rbp,rsp
> >           40110a:       mov    eax,0x0
> >           40110f:       pop    rbp
> >           401110:       ret
> >
> > Pass something from the command line to disable optimisations:
> >
> >         0000000000401126 <main>:
> >           401126:       push   rbp
> >           401127:       mov    rbp,rsp
> >           40112a:       sub    rsp,0x10
> >           40112e:       mov    DWORD PTR [rbp-0x4],edi
> >           401131:       mov    QWORD PTR [rbp-0x10],rsi
> >           401135:       mov    rax,QWORD PTR [rbp-0x10]
> >           401139:       add    rax,0x8
> >           40113d:       mov    rax,QWORD PTR [rax]
> >           401140:       mov    rdi,rax
> >           401143:       mov    eax,0x0
> >           401148:  ***  call   401030 <printf@plt>
> >           40114d:       mov    eax,0x0
> >           401152:       leave
> >           401153:       ret
> >
> > Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> > ---
> >
> >  scripts/cc-can-link.sh |    4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > --- a/scripts/cc-can-link.sh
> > +++ b/scripts/cc-can-link.sh
> > @@ -3,9 +3,9 @@
> >
> >  cat << "END" | $@ -x c - -o /dev/null >/dev/null 2>&1
> >  #include <stdio.h>
> > -int main(void)
> > +int main(int argc, char *argv[])
> >  {
> > -       printf("");
> > +       printf(argv[1]);
> >         return 0;
> >  }
> >  END
> 
> Ah, right.
> 
> But, we should not merge a bad coding example.
> 
> argv[1] may contain '%' format string, and
> recent GCC versions warn about it.
> 
> 
> 
> $ cat test.c
> #include <stdio.h>
> 
> int main(int argc, char *argv[])
> {
>     printf(argv[1]);
>     return 0;
> }
> $ gcc -c -o test.o  test.c
> test.c: In function ‘main’:
> test.c:5:5: warning: format not a string literal and no format
> arguments [-Wformat-security]
>     5 |     printf(argv[1]);
>       |     ^~~~~~

> I think replacing printf("") with printf("a")
> (or any string you like)
> is enough.

I get putchar() for "a". puts(argv[1]) works too.
I think argv[1] should be used to defeat optimisers, current and future.

      reply	other threads:[~2021-07-05 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 11:21 [PATCH] cc-can-link.sh: check for linking capability in a more robust way Alexey Dobriyan
2021-07-05 16:33 ` Masahiro Yamada
2021-07-05 21:22   ` Alexey Dobriyan [this message]

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=YON4AKdi9ISn3gvk@localhost.localdomain \
    --to=adobriyan@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.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