From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/4] more clang/sanitizer fixes
Date: Sat, 25 Jan 2020 00:35:42 -0500 [thread overview]
Message-ID: <20200125053542.GA744596@coredump.intra.peff.net> (raw)
Here are some more sanitizer fixes, this time from trying with clang-11.
These should go on top of jk/asan-build-fix if you want to get a
successful run with "make CC=clang-11 SANITIZE=address,undefined test".
I don't think any of them is indicative of a current bug in practice,
but the UBSan stuff makes me worried that an aggressive compiler might
do the wrong thing in some case.
[1/4]: merge-recursive: silence -Wxor-used-as-pow warning
[2/4]: avoid computing zero offsets from NULL pointer
[3/4]: xdiff: avoid computing non-zero offset from NULL pointer
[4/4]: obstack: avoid computing offsets from NULL pointer
compat/obstack.h | 6 ++++--
merge-recursive.c | 19 ++++++++++++++-----
sequencer.c | 6 +++---
unpack-trees.c | 2 +-
xdiff-interface.c | 12 ++++++++----
5 files changed, 30 insertions(+), 15 deletions(-)
-Peff
next reply other threads:[~2020-01-25 5:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 5:35 Jeff King [this message]
2020-01-25 5:37 ` [PATCH 1/4] merge-recursive: silence -Wxor-used-as-pow warning Jeff King
2020-01-25 17:27 ` Junio C Hamano
2020-01-25 19:55 ` Jeff King
2020-01-25 20:50 ` Elijah Newren
2020-01-25 23:57 ` Jeff King
2020-01-27 19:17 ` Junio C Hamano
2020-01-25 5:38 ` [PATCH 2/4] avoid computing zero offsets from NULL pointer Jeff King
2020-01-27 20:03 ` Junio C Hamano
2020-01-27 21:19 ` Jeff King
2020-01-28 18:03 ` Junio C Hamano
2020-01-29 2:31 ` Jeff King
2020-01-29 5:16 ` Junio C Hamano
2020-01-29 5:46 ` Jeff King
2020-01-25 5:39 ` [PATCH 3/4] xdiff: avoid computing non-zero offset " Jeff King
2020-01-25 5:41 ` [PATCH 4/4] obstack: avoid computing offsets " Jeff King
2020-01-25 5:44 ` [PATCH v2 " Jeff King
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=20200125053542.GA744596@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.