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

Re: [PATCH maint-1.6.5] block-sha1: avoid unaligned accesses on some big-endian systems

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Jul 14, 2012, 19:55 UTC
Message-ID
<CA+55aFwKYhUtXfaRcbOmMsvQW8p+h8N9PKpxW_y1kj6L=FQQNw@mail.gmail.com>
In-Reply-To
<20120714195022.GB23242@burratino>
On Sat, Jul 14, 2012 at 12:50 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> After the patch, what reason does gcc have to expect that 'block' is
> 32-bit aligned except when it is?  The code (including the code I
> didn't touch) never casts from char * to int * except in get/put_be32
> on arches that don't mind unaligned accesses.
Ahh. I was looking at the cast you added:
    blk_SHA1_Block(ctx, (const unsigned char *) ctx->W);

but I guess that if gcc inlines that and sees the original int type, it doesn't matter, because that *is* aligned.

So it's ok, but please just make blk_SHA1_Block() take a "const void *" instead and that cast can go away.

               Linus
Previous: Jonathan NiederNext: Jonathan Nieder
Message 4 of 10 in “block-sha1: avoid unaligned accesses on some big-endian systems”
  1. block-sha1: avoid unaligned accesses on some big-endian systemsJonathan Nieder, Jul 14, 2012
  2. Linus TorvaldsJul 14, 2012
  3. Jonathan NiederJul 14, 2012
  4. Linus TorvaldsJul 14, 2012
  5. block-sha1: avoid pointer conversion that violates alignment constraintsJonathan Nieder, Jul 14, 2012
  6. Linus TorvaldsJul 14, 2012
  7. block-sha1: put macro arguments in parenthesesJonathan Nieder, Jul 14, 2012
  8. Michael CreeJul 15, 2012
  9. Jonathan NiederJul 15, 2012
  10. Michael CreeJul 16, 2012

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.