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

Re: [PATCH] Makefile: use CXXFLAGS for linking fuzzers

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 14, 2018, 02:56 UTC
Message-ID
<xmqqsh04qsd6.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20181113185032.GC126896@google.com>
Josh Steadmon <steadmon@google.com> writes:
> OSS-Fuzz only provides one set of CXXFLAGS for use on both compiling
> project C++ project files as well linking the fuzzers themselves. So in
> the event that Git ever added any C++ sources, they would need to use
> the same set of CXXFLAGS.
OK.
> Given that, do you agree with Stefan that it is more intuitive to define
> CXXFLAGS next to the fuzzer build rules, since that's the only place
> it's used for now?

I am not sure. Until we gain other C++ targets (in other words, while linking with fuzzer is the only consumer of CXXFLAGS), I'd consider it similar to SPARSE_FLAGS and SPATCH_FLAGS, i.e. settings specific to an auxiliary tool that supports our development process, and it would make more sense to define it near them higher in the Makefile.

I'd probably feel differently if this were called FUZZ_CXXFLAGS or something like that, which would make its natural home next to the rule to build $(FUZZ_PROGRAMS), though.

Previous: Josh SteadmonNext: Josh Steadmon
Message 5 of 6 in “Makefile: use CXXFLAGS for linking fuzzers”
  1. Makefile: use CXXFLAGS for linking fuzzerssteadmon@google.com, Nov 12, 2018
  2. Stefan BellerNov 12, 2018
  3. Junio C HamanoNov 13, 2018
  4. Josh SteadmonNov 13, 2018
  5. Junio C HamanoNov 14, 2018
  6. Makefile: use FUZZ_CXXFLAGS for linking fuzzersJosh Steadmon, Nov 14, 2018

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.