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

Re: [RFC][PATCH 00/10] Sparse: Git's "make check" target

From
Josh Triplett <josh@freedesktop.org>
Date
Jun 9, 2007, 23:50 UTC
Message-ID
<466B3CC8.4010508@freedesktop.org>
In-Reply-To
<20070609225630.GC3008@uranus.ravnborg.org>
Sam Ravnborg wrote:
Show 7 quoted lines
>> Also, you might consider just using cgcc to run both GCC and Sparse.  That
>> would handle the issue of target-specific CFLAGS, by ensuring that Sparse and
>> GCC always see the same CFLAGS.
> 
> Is this the recommended way?
> I that case I suggest that someone looks into the linux kernel part
> and change it to use this method.

The approach taken by Linux allows running sparse on files without recompiling them. Using CC=cgcc just makes for less work, but the kernel has that work done now.

- Josh Triplett
Previous: Sam RavnborgNext: Ramsay Jones
Message 4 of 6 in “Sparse: Git's "make check" target”
  1. Ramsay JonesJun 8, 2007
  2. Josh TriplettJun 9, 2007
  3. Sam RavnborgJun 9, 2007
  4. Josh TriplettJun 9, 2007
  5. Ramsay JonesJun 12, 2007
  6. Josh TriplettJun 13, 2007

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.