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

Re: [PATCH 0/5] fix up 'jk/pack-bitmap' branch

From
Thomas Rast <tr@thomasrast.ch>
Date
Nov 9, 2013, 21:03 UTC
Message-ID
<87txflnv7n.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<527E7021.8060204@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 16 quoted lines
> Am 09.11.2013 12:35, schrieb Torsten Bögershausen:
>>
>> If I do like this in compat/bswap.h
>> 
>> # define ntohll(n) (n)
>> # define htonll(n) (n)
>> (on an Intel processor, little endian)
>> 
>> then t5310 passes, even if the uint64_t words are written
>> in little endian to disc instead of big endian.
>
> Of course. You write little endian and also read back little endian;
> that should work just fine, no?
>
> OTOH, if you write with Intel and read with PPC, then you should observe
> misbehavior with the above patch.

Maybe you could check in a simple test that the bitmap for a very predictable pack (e.g. only one commit) has a certain content, by checking its hash. That would guard against accidental format changes.

-- 
Thomas Rast
tr@thomasrast.ch
Previous: Johannes SixtNext: Jeff King
Message 9 of 10 in “fix up 'jk/pack-bitmap' branch”
  1. 0/5 fix up 'jk/pack-bitmap' branchRamsay Jones, Nov 7, 2013
  2. Jeff KingNov 7, 2013
  3. Vicent MartíNov 8, 2013
  4. Torsten BögershausenNov 8, 2013
  5. Ramsay JonesNov 8, 2013
  6. Jeff KingNov 8, 2013
  7. Torsten BögershausenNov 9, 2013
  8. Johannes SixtNov 9, 2013
  9. Thomas RastNov 9, 2013
  10. Jeff KingNov 9, 2013

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.