From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 3/4] cache.h: hex2chr() - avoid -Wsign-compare warnings
Date: Fri, 22 Sep 2017 17:24:00 +0100 [thread overview]
Message-ID: <d47cdae8-b37f-f378-6df6-bf70a819dd5b@ramsayjones.plus.com> (raw)
In-Reply-To: <20170922161159.hkw4id4kpnwo7jou@sigill.intra.peff.net>
On 22/09/17 17:11, Jeff King wrote:
> On Fri, Sep 22, 2017 at 05:05:03PM +0100, Ramsay Jones wrote:
>
>>> As an aside, I also see some uses of hexval() that don't appear to be
>>> quite as rigorous in checking for invalid characters. A few
>>> unconditionally shift the first nibble and assume that there will still
>>> be high bits set. I think that's generally true for twos-complement
>>> negative numbers, but isn't shifting off the left side of a signed
>>> integer undefined behavior?
>>
>> All uses of hexval() that I can see are shifting an unsigned value.
>> Have I missed something?
>
> Hmm. get_hex_color() does:
>
> unsigned int val;
> val = (hexval(in[0]) << 4) | hexval(in[1]));
>
> Isn't that shifting the signed return value of hexval(), and then
> converting it to unsigned afterwards?
Err ... no. the return value of hexval() is *unsigned int*.
(which is kinda the point!)
> I've been confused by C's integer conversion rules before, though, so
> perhaps I'm wrong.
>
> I think if this function is fed an empty string that it will also read
> past the end of the buffer for in[1]. It shouldn't matter, since the NUL
> in in[0] would cause us to return an error regardless, but it's still
> undefined behavior.
Correct.
> In fact, this whole function is just hex2chr() implemented badly. Who is
> responsible for this terrible code? ;)
;-)
ATB,
Ramsay Jones
next prev parent reply other threads:[~2017-09-22 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 16:48 [PATCH 3/4] cache.h: hex2chr() - avoid -Wsign-compare warnings Ramsay Jones
2017-09-22 5:47 ` Jeff King
2017-09-22 16:05 ` Ramsay Jones
2017-09-22 16:11 ` Jeff King
2017-09-22 16:18 ` Jeff King
2017-09-22 16:22 ` Jeff King
2017-09-22 16:24 ` Ramsay Jones [this message]
2017-09-22 18:01 ` René Scharfe
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d47cdae8-b37f-f378-6df6-bf70a819dd5b@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).