From: Brian Gerst <bgerst@didntduck.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Chris Wright <chrisw@sous-sol.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC, Announce] Unified x86 architecture, arch/x86
Date: Sat, 21 Jul 2007 07:34:47 -0400 [thread overview]
Message-ID: <46A1EF57.2020304@didntduck.org> (raw)
In-Reply-To: <1185005750.4012.100.camel@chaos>
Thomas Gleixner wrote:
> On Sat, 2007-07-21 at 07:37 +0200, Andi Kleen wrote:
>> On Saturday 21 July 2007 00:32, Thomas Gleixner wrote:
>>> As an initial matter, we made it painstakingly sure that the resulting
>>> .o files in a 32-bit build are bit for bit equal.
>> You got not a single line less code duplication then, so i don't really
>> see the point of this.
>
> Really ?
>
> The script detected 15 identical files with a simple cmp.
>
> It also unified another 10 by simply looking at the only line in there
> "include <the other arch/file>"
>
> And there is more of that, when you take the time and look closely at
> the _32.[ch] _64.[ch] files which are created by the merge.
Looking at the include files, many more are near-identical in trivial
ways, such as whitespace, comments, local variable names, or guard #ifdefs.
--
Brian Gerst
next prev parent reply other threads:[~2007-07-21 11:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 22:32 [RFC, Announce] Unified x86 architecture, arch/x86 Thomas Gleixner
2007-07-20 22:38 ` Jeff Garzik
2007-07-20 22:40 ` Ingo Molnar
2007-07-20 22:42 ` Jeff Garzik
2007-07-20 22:51 ` Linus Torvalds
2007-07-21 2:56 ` Yinghai Lu
2007-07-20 23:55 ` Alan Cox
2007-07-21 0:02 ` H. Peter Anvin
2007-07-21 22:26 ` Oleg Verych
2007-07-20 23:01 ` Arjan van de Ven
2007-07-20 23:23 ` Steven Rostedt
2007-07-21 2:39 ` Glauber de Oliveira Costa
2007-07-20 23:55 ` Michal Piotrowski
2007-07-21 0:03 ` Ingo Molnar
2007-07-21 0:16 ` Michal Piotrowski
2007-07-21 5:40 ` Andi Kleen
2007-07-21 5:50 ` Steven Rostedt
2007-07-21 6:06 ` Andi Kleen
2007-07-21 7:35 ` Adrian Bunk
2007-07-21 7:42 ` Andi Kleen
2007-07-21 8:01 ` Adrian Bunk
2007-07-21 8:15 ` Thomas Gleixner
2007-07-21 8:32 ` Ingo Molnar
2007-07-27 10:50 ` Pavel Machek
2007-07-27 18:11 ` Chris Wright
2007-07-20 23:55 ` Arnd Bergmann
2007-07-21 1:59 ` Steven Rostedt
2007-07-21 1:01 ` Gabriel C
2007-07-21 5:37 ` Andi Kleen
2007-07-21 5:58 ` Steven Rostedt
2007-07-21 6:09 ` Andi Kleen
2007-07-21 8:15 ` Thomas Gleixner
2007-07-21 8:28 ` Andi Kleen
2007-07-21 13:28 ` Glauber de Oliveira Costa
2007-07-21 9:02 ` Rusty Russell
2007-07-21 11:34 ` Brian Gerst [this message]
2007-07-21 12:30 ` Ingo Molnar
2007-07-21 15:11 ` Arjan van de Ven
2007-07-21 6:37 ` Avi Kivity
2007-07-21 10:37 ` David Woodhouse
2007-07-21 10:56 ` Adrian Bunk
2007-07-21 22:25 ` Matt Mackall
2007-07-21 23:51 ` Chris Wright
2007-07-22 7:50 ` Thomas Gleixner
2007-07-22 12:02 ` Matt Mackall
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=46A1EF57.2020304@didntduck.org \
--to=bgerst@didntduck.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox