From: Michael Tokarev <mjt@tls.msk.ru>
To: Rodrigo Rebello <rprebello@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-trivial] [PATCH v2 1/1] configure: use appropriate code fragment for -fstack-protector checks
Date: Sun, 29 Nov 2015 13:44:15 +0300 [thread overview]
Message-ID: <565AD6FF.6060105@msgid.tls.msk.ru> (raw)
In-Reply-To: <1447337068-2448-1-git-send-email-rprebello@gmail.com>
12.11.2015 17:04, Rodrigo Rebello wrote:
> The check for stack-protector support consisted in compiling and linking
> the test program below (output by function write_c_skeleton()) with the
> compiler flag -fstack-protector-strong first and then with
> -fstack-protector-all if the first one failed to work:
...
Applied to -trivial, thank you!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Rodrigo Rebello <rprebello@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] configure: use appropriate code fragment for -fstack-protector checks
Date: Sun, 29 Nov 2015 13:44:15 +0300 [thread overview]
Message-ID: <565AD6FF.6060105@msgid.tls.msk.ru> (raw)
In-Reply-To: <1447337068-2448-1-git-send-email-rprebello@gmail.com>
12.11.2015 17:04, Rodrigo Rebello wrote:
> The check for stack-protector support consisted in compiling and linking
> the test program below (output by function write_c_skeleton()) with the
> compiler flag -fstack-protector-strong first and then with
> -fstack-protector-all if the first one failed to work:
...
Applied to -trivial, thank you!
/mjt
next prev parent reply other threads:[~2015-11-29 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 14:04 [Qemu-trivial] [PATCH v2 1/1] configure: use appropriate code fragment for -fstack-protector checks Rodrigo Rebello
2015-11-12 14:04 ` [Qemu-devel] " Rodrigo Rebello
2015-11-12 16:10 ` [Qemu-trivial] " Markus Armbruster
2015-11-12 16:10 ` Markus Armbruster
2015-11-29 10:44 ` Michael Tokarev [this message]
2015-11-29 10:44 ` Michael Tokarev
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=565AD6FF.6060105@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rprebello@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.