linux-kernel - Re: "build-id" changes break sparc64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070723200500.3BBF94D058D@magilla.localdomain>
Date:	Mon, 23 Jul 2007 13:05:00 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Al Viro <viro@....linux.org.uk>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	Alan Modra <amodra@...pond.net.au>,
	Paul Mackerras <paulus@...ba.org>,
	David Miller <davem@...emloft.net>,
	Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org
Subject: Re: "build-id" changes break sparc64

> On Mon, Jul 23, 2007 at 12:12:15PM -0700, Roland McGrath wrote:
> > > rm vmlinux*; time make vmlinux
> > > 
> > > Vanilla tree: ~7,7 sec
> > > With single shot ld (Roland's patch): 8,3 secs
> > 
> > Shouldn't you compare:
> > 	rm vmlinux*; find . -name built-in.o -print | xargs rm
> > 	time make vmlinux
> > or something like that?
> 
> No.  You are talking about the time of full build; there it would
> be relevant.  For incrementals it's definitely not so.

Ah, I see what you are testing.  Well, a fair test then is to do something
that would actually happen, which is almost never just "rm vmlinux".
i.e., at least one ld -r -o foo/built-in.o from changing one source file.


Thanks,
Roland
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/