From: Josh Steadmon <steadmon@google.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net
Subject: [PATCH v2 0/2] fuzz: build fuzzers by default on Linux
Date: Thu, 11 Apr 2024 11:14:23 -0700 [thread overview]
Message-ID: <cover.1712858920.git.steadmon@google.com> (raw)
In-Reply-To: <cover.1709673020.git.steadmon@google.com>
Please note: this has been rebased onto the current 'master' [436d4e5b14
(The seventeenth batch, 2024-04-10)] in order to resolve a conflict with
the recently merged bt/fuzz-config-parse series.
Increase our protection against fuzzer bit-rot by making sure we can
link the fuzz test executables on Linux. Patch 1 is a small CI config
improvement to fix compiler feature detection. Patch 2 is the Makefile /
config.mak.uname change to add the executables to `make all` on Linux.
Changes in V2:
* Rebased onto master
* Fixed compiler mismatch issue when we override CC but not CXX
* Consolidated some of the fuzzer Makefile definitions in one location
Josh Steadmon (2):
ci: also define CXX environment variable
fuzz: link fuzz programs with `make all` on Linux
.github/workflows/main.yml | 12 +++++++
Makefile | 51 +++++++++++++++++------------
ci/run-build-and-minimal-fuzzers.sh | 2 +-
config.mak.uname | 1 +
4 files changed, 44 insertions(+), 22 deletions(-)
Range-diff against v1:
1: 75f98cbf98 ! 1: e55b691272 ci: also define CXX environment variable
@@ Commit message
'detect-compiler' script only looks at CC. Fix the issue by always
setting CXX to match CC in our CI config.
- We only plan on building fuzzers on Linux, so none of the other CI
- configs need a similar adjustment.
+ We only plan on building fuzzers on Linux with the next patch, so for
+ now, only adjust configuration for the Linux CI jobs.
2: eef15e3d3d < -: ---------- fuzz: link fuzz programs with `make all` on Linux
-: ---------- > 2: 8846a7766a fuzz: link fuzz programs with `make all` on Linux
base-commit: 436d4e5b14df49870a897f64fe92c0ddc7017e4c
--
2.44.0.683.g7961c838ac-goog
next prev parent reply other threads:[~2024-04-11 18:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:11 [PATCH 0/2] fuzz: build fuzzers by default on Linux Josh Steadmon
2024-03-05 21:11 ` [PATCH 1/2] ci: also define CXX environment variable Josh Steadmon
2024-03-05 21:37 ` Junio C Hamano
2024-04-09 21:32 ` Josh Steadmon
2024-03-06 0:50 ` Jeff King
2024-03-06 1:00 ` Jeff King
2024-04-10 20:58 ` Josh Steadmon
2024-03-05 21:12 ` [PATCH 2/2] fuzz: link fuzz programs with `make all` on Linux Josh Steadmon
2024-03-05 21:44 ` Junio C Hamano
2024-04-09 21:58 ` Josh Steadmon
2024-04-10 20:49 ` Josh Steadmon
2024-04-10 20:57 ` Junio C Hamano
2024-04-10 21:11 ` Jeff King
2024-03-26 21:51 ` [PATCH 0/2] fuzz: build fuzzers by default " Junio C Hamano
2024-04-09 21:34 ` Josh Steadmon
2024-04-11 18:14 ` Josh Steadmon [this message]
2024-04-11 18:14 ` [PATCH v2 1/2] ci: also define CXX environment variable Josh Steadmon
2024-04-12 4:22 ` Jeff King
2024-04-24 18:15 ` Josh Steadmon
2024-04-11 18:14 ` [PATCH v2 2/2] fuzz: link fuzz programs with `make all` on Linux Josh Steadmon
2024-04-11 21:39 ` Junio C Hamano
2024-04-24 18:14 ` [PATCH v3] " Josh Steadmon
2024-04-24 19:07 ` Junio C Hamano
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=cover.1712858920.git.steadmon@google.com \
--to=steadmon@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).