linux-kernel - Re: smart gcc inliner...

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]

Message-ID: <p73ircm4odz.fsf@bingen.suse.de>
Date:	27 Mar 2007 18:55:36 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Paweł Sikora <pluto@...k.net>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: smart gcc inliner...

Paweł Sikora <pluto@...k.net> writes:

> Hi,
> 
> The recent gcc (3.4/4.x) optimizer inlines functions across
> sections which is definitely not we want, e.g. inlining
> functions from .init.text section.
> 
> I think, the `__init' macro needs `noinline' attribute and all
> the `static inline __{dev}init' functions need `inline' attribute
> removal to avoid gcc error (inlining failed, function not inlinable).
> 

init functions should only ever be called from other init functions.

So this should not happen. If it happens the annotations need to be fixed.

This is already warned for for modules at build time with pending
patches to do the same for vmlinux.

There are already a couple of patches pending for this and many 
went into .21.

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