From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932730AbbJ0Ozw (ORCPT ); Tue, 27 Oct 2015 10:55:52 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:44157 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932663AbbJ0Ozu (ORCPT ); Tue, 27 Oct 2015 10:55:50 -0400 Message-Id: <1445957749.1388742.421558841.29441B00@webmail.messagingengine.com> X-Sasl-Enc: BdeoBuAMB49twijAngb9xjutjwFCE5d520DaBCRhR1Dw 1445957749 From: Hannes Frederic Sowa To: Denys Vlasenko , Linux Kernel Mailing List , Oleg Nesterov MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-25d3ec43 Subject: Re: Inline hunt results for 4.3.0-rc1 Date: Tue, 27 Oct 2015 15:55:49 +0100 In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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