From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Support SPARSE in Makefile, better SPARSE_FLAGS
Date: Fri, 30 Sep 2005 15:16:48 -0700 [thread overview]
Message-ID: <433DB950.3010909@zytor.com> (raw)
In-Reply-To: <1128118469.7352.15.camel@dv>
Pavel Roskin wrote:
>
> I know. That's what I'm using in the wrapper (plus -m64 and some
> warnings). But it should be the default. Until then, hassle-free
> sparse support in the Makefile is only possible for the projects that
> already know the architecture (e.g. the Linux kernel).
>
I think that's debatable. It introduces main-compiler dependencies into
sparse which is undesirable.
A much simpler option would be to write a "sparsegcc" script which would
be invoked just like gcc, extract the appropriate macro information
based on options, and then invoke sparse.
-hpa
next prev parent reply other threads:[~2005-09-30 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 20:46 [PATCH] Support SPARSE in Makefile, better SPARSE_FLAGS Pavel Roskin
2005-09-30 5:46 ` Junio C Hamano
2005-09-30 13:41 ` Pavel Roskin
2005-09-30 19:19 ` H. Peter Anvin
2005-09-30 22:14 ` Pavel Roskin
2005-09-30 22:16 ` H. Peter Anvin [this message]
2005-10-01 4:13 ` Pavel Roskin
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=433DB950.3010909@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=proski@gnu.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.