Comments (3)
The CRC hash functions are somewhat unique because they are bit-wise hash functions instead of byte-wise hash functions. The bit-endianness of the bytes will be whatever the endianness of the machine is, but that shouldn't matter because the only thing that should matter is the order of the bits.
Since they are bit-wise, the standards specify the endianness that input bytes should be processed and the endianness of the outputted bytes. This is controlled by the reflectIn and reflectOut fields in https://github.com/brandondahler/Data.HashFunction/blob/master/CRC/Standards.json . Since ARC specifies reflectIn and reflectOut as both true, it should process and produce a bitstream that is big-endian.
The good news for you is that this is already handled and you'll find that the bitstream produced by any other endianness machine will produce the same bitstream as you will receive if you do the following:
...
var crc = new System.Data.HashFunction.CRCStandards.ARC();
var bytes = crc.ComputeHash(System.Text.Encoding.UTF8.GetBytes("123456789"));
var bitArray = new BitArray(bytes);
// Should write 1011101100111101
foreach (var bit in bitArray)
Console.Write((bit ? 1 : 0));
Console.WriteLine();
...
The only thing you might need to be concerned with is the bit-endianness of the bytes when you transmit bytes between the systems -- either the sender needs to convert its bytes from its native endianness to the receivers endianness, or the reciever will need to convert the recieved bytes from the other's endianness its endianness.
Reguardless of the endianness of any of the machines, casting the bytes to a short on the producing machine and printing them out should produce the decimal value 47,933.
from data.hashfunction.
I'm afraid you are misunderstanding byte endianess and the way that hexadecimal values are expressed.
When we write the value 0xBB3D, we are expressing them in big-endian as that is how we naturally express numbers in everyday life -- 0xBB3D == 47,933 dec, just like how 0x003D == 61 dec. However, most modern-day, laptop/desktop processors work in little-endian. What this means is that when you read the value 0xBB3D as individual bytes that the computer stores, you'll read it as { 0x3D, 0xBB }.
To put it programmatically, run the following code:
...
var crc = new System.Data.HashFunction.CRCStandards.ARC();
var bytes = crc.ComputeHash(System.Text.Encoding.UTF8.GetBytes("123456789"));
var shortValue = BitConverter.ToUInt16(bytes);
// Should print BB3D
Console.WriteLine(shortValue.ToString("X"));
...
Let me know if you have any other questions or concerns.
from data.hashfunction.
Hi Brandon,
I apologize for not explaining myself correctly (probably a moment of stupidity towards the weekend :-) ). What endianess does the library produce? is it always little? big? or does it vary based on platform? In order for me to compare the CRC the library produces to a CRC provided in a byte stream that has been coded using big endian I need to know the order to compare the bytes.
from data.hashfunction.
Related Issues (20)
- Support for stream block processing HOT 5
- Performance HOT 2
- AsHexstring() function in CityHash gives reverse output HOT 4
- CRC Hash Error HOT 1
- Example in README is wrong signature HOT 1
- add t1ha (Fast Positive Hash) HOT 1
- Valid hash size for xxHash HOT 1
- Re-namespace and rename packages HOT 2
- Move LICENSE file include to Directory.Build.props
- Better separate hash functions that aren't variable size into distinct types.
- Review and normalize XML comments and function parameters
- Ensure cross-implementation consistency in variable names
- Re-order using statements
- Ensure 100% test coverage
- Support Span<byte> as Hash-function input
- announcement: PowerShell Module with this Hash functions
- Different strings, but the xxHash calculation result is the same HOT 1
- xxHash gives incorrect value when using AsHexString method. HOT 4
- Result of CityHash64 doesn't match the reference implementation on strings of 64*n (n > 1) lengths
- Outdated CityHash NuGet package with too slow 128-bit implementation HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from data.hashfunction.