[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080427055943.GA16290@elte.hu>
Date: Sun, 27 Apr 2008 07:59:43 +0200
From: Ingo Molnar <mingo@...e.hu>
To: David Miller <davem@...emloft.net>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, viro@...IV.linux.org.uk
Subject: Re: CONFIG_OPTIMIZE_INLINING
* David Miller <davem@...emloft.net> wrote:
> Ingo, why the heck is this hiding under arch/x86/ and not in
> lib/Kconfig.debug where it belongs?
>
> x86: add optimized inlining
>
> If there are platforms that can't handle it, we can add a conditional
> to lib/Kconfig.debug, but by default it should be made available
> generically.
>
> Where did this original patch get posted for review and discussion?
>
> Tell me where!?!?!
here, two months ago:
http://lkml.org/lkml/2008/3/3/122
i made it x86-only due to this FUD that went against it:
"messing with a global #define in a way that the results on 24
architectures with 7 different releases of gcc would be
unpredictable."
... as i saw no reason why this feature, which i found rather useful,
should be delayed another year or so. I'd be more than happy to promote
this feature back to lib/Kconfig.debug, sparc64 interest would make that
a strong argument.
and here is the pull request that i posted to lkml, with the full patch
included as well:
http://www.gossamer-threads.com/lists/linux/kernel/911104?page=last
> The only references I see is where Stephen Rothwell complained that it
> broke the powerpc build, and then on the git commit list when Linus
> sucked this crud in.
i think there must something wrong about your lkml feed.
Ingo
--
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/
Powered by blists - more mailing lists