From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][SPARSE] Runtime detection of gcc include paths
Date: 8 Jun 2003 20:51:18 -0700 [thread overview]
Message-ID: <bc107m$ue3$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0306081807500.1849-100000@home.transmeta.com
Followup to: <Pine.LNX.4.44.0306081807500.1849-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> On Sun, 8 Jun 2003, Ryan Anderson wrote:
> >
> > This uses the same method as previously was used, it just performs the
> > lookup at runtime.
>
> I much prefer a compile-time thing.
>
> Performance is, to me, paramount for "checker". I don't want to slow it
> down, I'm hoping that some day we can just enable C=1 by default in the
> kernel build (this is a _long_ time off, though, don't you all start
> worrying now).
>
> I don't see anything wrong with a compile/install time thing, that is,
> after all, how gcc too works.
>
Both of these seem a little unnecessary. Why not pass this stuff on
the command line, and have the top-level Makefile extract the paths
into a command-line argument?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
prev parent reply other threads:[~2003-06-09 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 1:11 [PATCH][SPARSE] Runtime detection of gcc include paths Ryan Anderson
2003-06-09 1:09 ` Linus Torvalds
2003-06-09 3:51 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bc107m$ue3$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.