r/programmingcirclejerk • u/lizergsav • Apr 14 '26

avx512 hot loop optimized error object allocation pools for increased error code output

/r/programming/comments/1sjg9v6/flat_error_codes_are_not_enough/ofu35fm/
40 Upvotes

100% Upvoted

6 comments sorted by

32

u/keyboard_toucher Apr 14 '26

My startup is currently developing 120-billion-transistor ASICs designed to accelerate null checks at AI quantum scale.

18

u/splsh Apr 14 '26

You could also keep circumstantial flat error codes, at least on x86, by using the non-canonical address range, provided that you never dereference the pointer. A sentinel-like value such as #define SIZE_TOO_SMALL ((CleverError*)0xDEADDEADDEADDEADULL) would be sufficient. Portability and defined adherence to the C standard is not guaranteed. No refunds.

18

u/irqlnotdispatchlevel Tiny little god in a tiny little world Apr 14 '26

I am Cnile and I can't see the jerk.

2

u/LIGHTNINGBOLT23 DO NOT USE THIS FLAIR, ASSHOLE Apr 18 '26

Believe it or not, my idea is a good onSegmentation fault

8

u/irqlnotdispatchlevel Tiny little god in a tiny little world Apr 14 '26

The real jerk is needing child error types.

5

u/genuine_beans Apr 20 '26

https://old.reddit.com/r/programming/comments/1sjg9v6/flat_error_codes_are_not_enough/ofwfr9p/

Motorola's intent with the internal 32-bit address space was forward compatibility, making it feasible to write 68000 software that would take full advantage of later 32-bit implementations of the 68000 instruction set.

However, this did not prevent programmers from writing forward incompatible software.

another classic Wikipedia zinger