[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090912054906.22b05848@infradead.org>
Date: Sat, 12 Sep 2009 05:49:06 +0200
From: Arjan van de Ven <arjan@...radead.org>
To: Roland McGrath <roland@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org, jakub@...hat.com,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
x86@...nel.org
Subject: Re: [PATCH 1/2] UNREACHABLE() macro
On Fri, 11 Sep 2009 14:55:25 -0700 (PDT)
Roland McGrath <roland@...hat.com> wrote:
> > That's a bit of a mouthful. Did you consider a runtime probe with
> > scripts/Kbuild.include's try-run, cc-option, etc?
>
> I did not see any precedent in the sources for using those to test for
> features by compiling particular test sources (i.e. in autoconf
look at the stackprotector flags.. they work this way already.
It gets done once per kernel build...
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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