linux-kernel - Re: [PATCH 3/3] build system: section garbage collection for vmlinux

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 10 Sep 2007 21:14:02 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] build system: section garbage collection for vmlinux

On Mon, Sep 10, 2007 at 08:02:15PM +0100, Denys Vlasenko wrote:
> On Monday 10 September 2007 13:01, Sam Ravnborg wrote:
> > > 
> > > > Doing a normal kernel build will link vmlinux three or four times.
> > > > If we introduce --gc-sections we should add a preparational link of
> > > > vmlinux where we use --gc-sections and skip it for the rest of the links
> > > > assuming that --gc-sections takes some time for ld to do.
> > > 
> > > Yes, this will speed up things a bit.
> > 
> > If we do the --gc-sections trick during the preparational link then we do
> > not use the arch supplied linker script.
> > Will it be possible to create a dedicated linker script that is valid
> > for all architectures and which only include the KEEP() directives for
> > the diverse sections?
> 
> Unfortunately, -r and --gc-sections don't mix.
> 
> x86_64-pc-linux-gnu-ld: --gc-sections and -r may not be used together
OK - so much for that optimization :-(

But then we need to annotate ALL arch linker script before introducing this.
And that bring me back to that we should put some sanity into these first.

	Sam
-
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/