From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: lkp@lists.01.org
Subject: 18aa8a45 +1.03% kernel-size.text
Date: Mon, 17 Nov 2014 12:01:03 +0800 [thread overview]
Message-ID: <20141117040103.GO300@yliu-dev.sh.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Hi Kees,
JFYI, we noticed that your following commit make the kernel size a bit
larger: 1.03%
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git gcc-bug
perf change: 1.03% kernel-size.text
RESULT_ROOT: /result/wsm/boot/performance-1/debian-x86_64.cgz/x86_64-rhel/8562cc73288ff2f399625e2965b8f5cc644b5401/0
18aa8a45645640c7a44d15ebb7cb2270d3c23af8 is the first bad commit
commit 18aa8a45645640c7a44d15ebb7cb2270d3c23af8
Author: Kees Cook <keescook@chromium.org>
AuthorDate: Wed May 7 10:50:04 2014 -0700
Commit: Kees Cook <keescook@chromium.org>
CommitDate: Fri Nov 14 13:35:42 2014 -0800
build: re-enable size builtin for gcc 4.8 and later
Most cases of strict copy from/to user checking are caught by gcc
now. This re-enables it for gcc 4.8 and later so the gcc bug can be
explored.
Signed-off-by: Kees Cook <keescook@chromium.org>
include/linux/compiler-gcc4.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--yliu
reply other threads:[~2014-11-17 4:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141117040103.GO300@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=lkp@lists.01.org \
/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.