Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] qemu: add patch to fix SSP support detection
Date: Thu, 12 Nov 2015 09:19:41 +0100	[thread overview]
Message-ID: <56444B9D.3060501@mind.be> (raw)
In-Reply-To: <CABLs7GXMFP-vm1tRx1zcQZAsJ+KXUV8JNqxLN+3qPhGbNDL50w@mail.gmail.com>



On 12-11-15 00:49, Rodrigo Rebello wrote:
> Arnout,
> 
> 2015-11-11 21:30 GMT-02:00 Arnout Vandecappelle <arnout@mind.be>:
>> On 11-11-15 23:18, Rodrigo Rebello wrote:
[snip]
>>> +diff --git a/configure b/configure
>>> +index cd219d8..a6f4101 100755
>>> +--- a/configure
>>> ++++ b/configure
>>> +@@ -1471,6 +1471,24 @@ for flag in $gcc_flags; do
>>> + done
>>> +
>>> + if test "$stack_protector" != "no"; then
>>> ++  cat > $TMPC << EOF
>>> ++void foo(const char *c);
>>
>>  This declaration is unnecessary.
>>
> 
> Actually it is necessary, otherwise compiling the test code fails with:
> 
> config-temp/qemu-conf.c:3:6: error: no previous prototype for ?foo?
> [-Werror=missing-prototypes]
>  void foo(const char *c)
>       ^
> 
> Because in configure, line 410, -Wmissing-prototypes is added to
> QEMU_FLAGS (used in every compile test), and tests are run with
> -Werror by default, unless --disable-werror is passed to the configure
> script.

 Right. And I guess declaring it static means that the whole function could be
elided so still no stack protection.

 I wonder what would happen if LTO were enabled, since in that case the function
could be elided again...

 To solve this fundamentally in buildroot, perhaps we should patch the gcc
wrapper to fail when -fstack-protector-* is passed when SSP is not enabled.

 Regards,
 Arnout

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-11-12  8:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 22:18 [Buildroot] [PATCH v2 1/1] qemu: add patch to fix SSP support detection Rodrigo Rebello
2015-11-11 23:30 ` Arnout Vandecappelle
2015-11-11 23:49   ` Rodrigo Rebello
2015-11-12  8:19     ` Arnout Vandecappelle [this message]
2015-11-12 15:04       ` Rodrigo Rebello
2015-11-13  7:10         ` Arnout Vandecappelle
2015-11-14  3:32           ` Rodrigo Rebello
2015-11-16  6:32             ` Arnout Vandecappelle
2015-11-16 10:15               ` Rodrigo Rebello

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=56444B9D.3060501@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.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