| Age | Commit message (Collapse) | Author |
|---|
|
The previous behaviour was correct. A width of 1900 pixels which is
0x00000640 in hex was stored on disk as:
00 00 06 40
That's BE order which is what we want.
Reading this uint32_t on an LE machine we get:
width = 0x40060000 and converting from BE to LE
we get the correct 0x640 value.
Reading on a BE machine we get the correct value
and the swap is a no-op.
|
|
Well, who would have thought fwrite already converts your integer to
NBO? It would've been bloody helpful to at least mention it in the
manual.
While at it, fix the wrong read-in-code and call it a day.
|
|
|
|
These tools are "one-shot", nobody cares about memory leaks while
the program is running.
Bring back -Os, no more false positives because there's no interaction
between gotos and setjmp/longjmp.
|
|
We could use the macros from stdint.h but this should be good
enough.
|
|
|
|
If we fail early, the call to free(png_row) could crash because
of an uninitialized (non-NULL) png_row.
|
|
|
|
-Os generates lots of false positives and it is not worth it much
for such a small set of tools.
|
|
Respectively, image.png will become an image.if
|
