From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Martin Liška" <mliska@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Fix nonnull errors reported by UBSAN with GCC 7.
Date: Thu, 6 Apr 2017 10:57:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704061056020.4268@virtualbox> (raw)
In-Reply-To: <295981e7-d2e9-d3db-e32d-8dd80ca47136@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Hi Martin,
On Thu, 6 Apr 2017, Martin Liška wrote:
> Following patch fixes issues that can be seen with -fsanitize=undefined
> on GCC 7.
The commit message says:
Memory functions like memmove and memcpy should not be called
with an argument equal to NULL.
But the patch is not about the pointer arguments, it is about the size
argument. So I would suggest to say
Memory functions like memmove and memcpy should only be called
with positive sizes.
Ciao,
Johannes
prev parent reply other threads:[~2017-04-06 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 8:02 [PATCH 1/2] Fix nonnull errors reported by UBSAN with GCC 7 Martin Liška
2017-04-06 8:34 ` Jeff King
2017-04-06 9:52 ` [PATCH v2 " Martin Liška
2017-04-06 12:26 ` René Scharfe
2017-04-06 15:42 ` [PATCH v3 " Martin Liška
2017-04-06 16:33 ` Johannes Sixt
2017-04-06 17:31 ` René Scharfe
2017-04-06 20:49 ` Johannes Sixt
2017-04-07 14:23 ` Martin Liška
2017-04-07 15:25 ` René Scharfe
2017-04-07 15:25 ` [PATCH 1/2] add MOVE_ARRAY René Scharfe
2017-04-07 15:25 ` [PATCH 2/2] use MOVE_ARRAY René Scharfe
2017-04-17 1:49 ` [PATCH v3 1/2] Fix nonnull errors reported by UBSAN with GCC 7 Junio C Hamano
2017-04-17 7:59 ` Johannes Sixt
2017-04-06 8:57 ` Johannes Schindelin [this message]
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=alpine.DEB.2.20.1704061056020.4268@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=mliska@suse.cz \
/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.