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
Sep 30, 2005, 22:14 UTC
Message-ID
<1128118469.7352.15.camel@dv>
In-Reply-To
<433D8FA6.2080808@zytor.com>
On Fri, 2005-09-30 at 12:19 -0700, H. Peter Anvin wrote:
Show 11 quoted lines
> Pavel Roskin wrote:
> > 
> > I hate to say that, but a better alternative is to fix sparse to act
> > like the native compiler by default (possibly with options to imitate
> > other architectures or to be fully arch-neutral).
> > 
> 
> $(CC) $(CFLAGS) -E -dM -x c /dev/null -o builtin.h
> 
> ... will output a file containing all the buildin macros that you can 
> feed to sparse with -include.

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

-- 
Regards,
Pavel Roskin
Previous: H. Peter AnvinNext: H. Peter Anvin
Message 5 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.