LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com> To: Joe Perches <joe@perches.com> Cc: Matthew Wilcox <matthew@wil.cx>, LKML <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@linux-foundation.org>, linux-fsdevel@vger.kernel.org, gcc@gcc.gnu.org Subject: Re: [PATCH] linux/fs.h - Convert debug functions declared inline __attribute__((format (printf,x,y) to statement expression macros Date: Tue, 26 Feb 2008 23:38:10 -0800 (PST) [thread overview] Message-ID: <alpine.DEB.1.00.0802262319350.11433@chino.kir.corp.google.com> (raw) In-Reply-To: <1204095249.19319.444.camel@localhost> On Tue, 26 Feb 2008, Joe Perches wrote: > > I'm not seeing any change in text size with allyesconfig after applying > > this patch with latest git: > > This is just x86 defconfig > allyesconfig should be able to capture any text savings that this patch offers. > > Joe, what version of gcc are you using? > > $ gcc --version > gcc (GCC) 4.2.2 20071128 (prerelease) (4.2.2-3.1mdv2008.0) > My x86_64 defconfig with gcc 4.0.3 had no difference in text size after applying your patch, yet the same config on gcc 4.1.2 did: text data bss dec hex filename 5386112 846328 719560 6952000 6a1440 vmlinux.before 5386048 846328 719560 6951936 6a1400 vmlinux.after
next prev parent reply other threads:[~2008-02-27 7:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-27 3:08 [PATCH] linux/kernel.h linux/device.h - Convert debug functions declared inline __attribute__((format (printf,x,y) to statement expression macros Joe Perches 2008-02-27 4:02 ` [PATCH] linux/fs.h " Joe Perches 2008-02-27 4:13 ` Matthew Wilcox 2008-02-27 4:55 ` Joe Perches 2008-02-27 5:44 ` David Rientjes 2008-02-27 6:54 ` Joe Perches 2008-02-27 7:38 ` David Rientjes [this message] 2008-02-27 22:58 ` David Rientjes 2008-02-27 23:58 ` Jan Hubicka 2008-02-28 8:28 ` David Rientjes 2008-02-28 8:42 ` Jakub Jelinek 2008-02-28 10:23 ` Jan Hubicka 2008-02-29 1:09 ` Joe Perches 2008-03-23 15:22 ` Denys Vlasenko 2008-03-24 19:52 ` Joe Perches
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=alpine.DEB.1.00.0802262319350.11433@chino.kir.corp.google.com \ --to=rientjes@google.com \ --cc=gcc@gcc.gnu.org \ --cc=joe@perches.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=matthew@wil.cx \ --cc=torvalds@linux-foundation.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: linkBe 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; as well as URLs for NNTP newsgroup(s).