From: James Hogan <jhogan@kernel.org>
To: Matt Turner <mattst88@gmail.com>
Cc: linux-mips@linux-mips.org, Arnd Bergmann <arnd@arndb.de>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha <linux-alpha@vger.kernel.org>,
linux-arch@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/3] alpha: Use OPTIMIZE_INLINING instead of asm/compiler.h
Date: Mon, 7 May 2018 09:42:41 +0100 [thread overview]
Message-ID: <20180507084240.GA26491@jamesdev> (raw)
In-Reply-To: <CAEdQ38HfabRWgfLTStuZDOz0yjnfMNRc5beRdVcQhFfMi1SFKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
On Sun, May 06, 2018 at 12:33:21PM -0700, Matt Turner wrote:
> On Tue, Apr 17, 2018 at 3:11 AM, James Hogan <jhogan@kernel.org> wrote:
> > Use CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING and CONFIG_OPTIMIZE_INLINING
> > instead of undefining the inline macros in the alpha specific
> > asm/compiler.h. This is to allow asm/compiler.h to become a general
> > header that can be used for overriding linux/compiler*.h.
> >
> > A build of alpha's defconfig on GCC 7.3 before and after this series
> > (i.e. this commit and "compiler.h: Allow arch-specific overrides" which
> > includes asm/compiler.h from linux/compiler_types.h) results in the
> > following size differences, which appear harmless to me:
> >
> > $ ./scripts/bloat-o-meter vmlinux.1 vmlinux.2
> > add/remove: 1/1 grow/shrink: 3/0 up/down: 264/-348 (-84)
> > Function old new delta
> > cap_bprm_set_creds 1496 1664 +168
> > cap_issubset - 68 +68
> > flex_array_put 328 344 +16
> > cap_capset 488 500 +12
> > nonroot_raised_pE.constprop 348 - -348
> > Total: Before=5823709, After=5823625, chg -0.00%
> >
> > Suggested-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: James Hogan <jhogan@kernel.org>
> > Cc: Richard Henderson <rth@twiddle.net>
> > Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
> > Cc: Matt Turner <mattst88@gmail.com>
> > Cc: linux-alpha@vger.kernel.org
>
> Looks fine to me.
>
> Acked-by: Matt Turner <mattst88@gmail.com>
Thanks
>
> Should I take it through the alpha tree?
I'll take all 3 through the MIPS tree if thats okay with you, as its a
prerequisite to allowing MIPS to override stuff in linux/compiler-gcc.h
using asm/compiler.h, which is needed to fix build breakage in 4.17.
Thanks
James
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-05-07 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:11 [PATCH v3 0/3] MIPS: Override barrier_before_unreachable() to fix microMIPS James Hogan
2018-04-17 10:11 ` [PATCH v3 1/3] alpha: Use OPTIMIZE_INLINING instead of asm/compiler.h James Hogan
2018-05-06 19:33 ` Matt Turner
2018-05-07 8:42 ` James Hogan [this message]
2018-05-07 16:03 ` Matt Turner
2018-04-17 10:11 ` [PATCH v3 2/3] compiler.h: Allow arch-specific overrides James Hogan
2018-04-17 19:19 ` kbuild test robot
2018-04-17 19:19 ` kbuild test robot
2018-04-17 19:19 ` kbuild test robot
2018-04-17 21:04 ` James Hogan
2018-04-17 10:11 ` [PATCH v3 3/3] MIPS: Workaround GCC __builtin_unreachable reordering bug James Hogan
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=20180507084240.GA26491@jamesdev \
--to=jhogan@kernel.org \
--cc=arnd@arndb.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.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 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.