git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Support SPARSE in Makefile, better SPARSE_FLAGS

From
PRPavel Roskin <proski@gnu.org>
Date
Oct 1, 2005, 04:13 UTC
Message-ID
<20051001001358.n59rjyg48400c0kw@webmail.spamcop.net>
In-Reply-To
<433DB950.3010909@zytor.com>
Quoting "H. Peter Anvin" <hpa@zytor.com>:
Show 10 quoted lines
> 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.

I see sparse is already moving in this direction. Right now, it's somewhere in the middle, which is quite inconvenient. It hardcodes gcc version numbers but not the architecture.

> 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.

I guess that's what cgcc is trying to be. Since it also runs the compiler, no special support for cgcc should be needed in Makefile other than using $(CC).

-- Regards, Pavel Roskin

Previous: H. Peter Anvin
Message 7 of 7 in “Support SPARSE in Makefile, better SPARSE_FLAGS”
  1. Support SPARSE in Makefile, better SPARSE_FLAGSPavel Roskin, Sep 29, 2005
  2. Junio C HamanoSep 30, 2005
  3. Pavel RoskinSep 30, 2005
  4. H. Peter AnvinSep 30, 2005
  5. Pavel RoskinSep 30, 2005
  6. H. Peter AnvinSep 30, 2005
  7. Pavel RoskinOct 1, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.