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

unary minus operator applied to unsigned type, result still unsigned?

From
Philip Oakley <philipoakley@iee.org>
Date
May 4, 2016, 22:59 UTC
Message-ID
<74B59A4DF45C45AF9CDCF6662DDAEF1E@PhilipOakley>

I'm working on building Git on Visual Studio as part of the Git for Windows capability.

The MSVC compiler is reporting:

1>..\sha1-lookup.c(100) : warning C4146: unary minus operator applied to unsigned type, result still unsigned

1>..\sha1-lookup.c(316) : warning C4146: unary minus operator applied to unsigned type, result still unsigned

the two lines of code are the same, and the message suggests a bad return value:

#100: return -lo-1;
#316: return -lo-1;

Should these be protected by an appropriate brackets/calculation (-1-lo) ? Or does gcc use an alternate assumption about unary minus conversion for functions returning int?

--
Philip
Next: Junio C Hamano
Message 1 of 3 in “unary minus operator applied to unsigned type, result still unsigned?”
  1. Philip OakleyMay 4, 2016
  2. Junio C HamanoMay 4, 2016
  3. Philip OakleyMay 5, 2016

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.