mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Denys Vlasenko <vda.linux@googlemail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>
Subject: Re: Inline hunt results for 4.3.0-rc1
Date: Tue, 27 Oct 2015 15:55:49 +0100	[thread overview]
Message-ID: <1445957749.1388742.421558841.29441B00@webmail.messagingengine.com> (raw)
In-Reply-To: <CAK1hOcNPPVLkDBTvTxBmexPyGYJ5+H51D76JsROHmEoVipFfwQ@mail.gmail.com>

Hello,

On Tue, Oct 27, 2015, at 15:32, Denys Vlasenko wrote:
> I have created a set of semi-automated scripts which look for
> large inlines in the kernel.
> 
> Recently I taught it to even generate "git format-patch" patches
> (unfortunately, only for inlines in *.c files, not *.h),
> and here are they for 4.3.0-rc1 - i.e. current Linus tree.
> 
> Submitting 300+ patches separately would amount to spamming,
> instead I encourage people to take a look at the patches
> on the Web:
> 
>     http://busybox.net/~vda/inline_hunt/4.3.0-rc1/
>     http://busybox.net/~vda/inline_hunt/4.3.0-rc1/README
> 
> and in particular, at the set of most juicy patches, each of which
> shaves off more than 1000 bytes off its *.c module:
> 
>     http://busybox.net/~vda/inline_hunt/4.3.0-rc1/patch_saves1000/

Does gcc -finline-limit=2000 somehow has the same effect?

Thanks,
Hannes

  reply	other threads:[~2015-10-27 14:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 14:32 Denys Vlasenko
2015-10-27 14:55 ` Hannes Frederic Sowa [this message]
2015-10-27 15:17   ` Denys Vlasenko
2015-10-27 15:25     ` Hannes Frederic Sowa
2015-10-27 15:31 ` Peter Hurley
2015-10-29  9:33 ` Denys Vlasenko

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=1445957749.1388742.421558841.29441B00@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=vda.linux@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®