On Thu, 2008-01-31 at 23:53 -0500, George Spelvin wrote:
> The code to fill it in is smaller than the table itself.
> Is it worth complicating things with some INIT code to reduce
> the stored image size? (The table is not compressible.)
[snip]
Thanks but since the code is only used when
On Thu, 2008-01-31 at 23:53 -0500, George Spelvin wrote:
The code to fill it in is smaller than the table itself.
Is it worth complicating things with some INIT code to reduce
the stored image size? (The table is not compressible.)
[snip]
Thanks but since the code is only used when building
George Spelvin wrote:
The code to fill it in is smaller than the table itself.
Is it worth complicating things with some INIT code to reduce
the stored image size? (The table is not compressible.)
I think it matters not at all either way.
-hpa
--
To unsubscribe from this list: send
The code to fill it in is smaller than the table itself.
Is it worth complicating things with some INIT code to reduce
the stored image size? (The table is not compressible.)
#define CRC32POLY 0xedb88320 /* CRC32 polynomial, little-endian */
static uint32_t crctab32[256];
void
The code to fill it in is smaller than the table itself.
Is it worth complicating things with some INIT code to reduce
the stored image size? (The table is not compressible.)
#define CRC32POLY 0xedb88320 /* CRC32 polynomial, little-endian */
static uint32_t crctab32[256];
void
George Spelvin wrote:
The code to fill it in is smaller than the table itself.
Is it worth complicating things with some INIT code to reduce
the stored image size? (The table is not compressible.)
I think it matters not at all either way.
-hpa
--
To unsubscribe from this list: send
6 matches
Mail list logo
