> In hindsight maybe a binary level translator from 8080 to 8086 would have worked better (and be simple enough) Many programs written in assembly language used self modifying code back then. It saved RAM and improved…
Linux does not dragged down in performance by the thousands of virus and malware scanners.
ARM riding the "everything is AI" train. So sad.
Yea.. having fun with war.. Most American post I have seen here since ages.
The fun thing was the Roland Sync. You could sync up all the TB-303, TB-909 and all the others with a 5-pole DIN cable. The sync was badly implemented. It lagged, it had latency. However! As soon as you cabled all…
Easy, it is dopamine.
Back then Microsoft was lobbying as hard as they could to turn that decision to move to linux over. They knew: If Linux makes it in Munich, it will likely spread over and they loose tons of contracts with other German…
"I could only find a couple tutorials/guides and both were imperative" Aren't Quadtrees covered by almost all basic data-structure books? It is the most simple form of taking the binary tree into the next (2D) dimension.
this For those who don't know: Vias are not only used to get an electrical connection from one side of the PCB to another. You also need them to keep radiation in check and often to move heat away. With this technique,…
Honestly, this is really bad. It might be a breakthrough of what you are doing, but when I listen to the output all of the timing and phrasing is aweful.
There are couple of tricks you can do if you fiddle with the bits of a floating point value using integer arithmetic and binary logic. That was a thing back in the 90th.. I wonder how hard the performance hit from…
> 1. Apple having just announced it is opening up NFC > to developers means that both major mobile > platforms can now act as responding devices; > 2. Mobile consumer hardware is sufficiently fast for the application >…
I've worked in the payment industry and among other things built a payment terminal, so I know a thing or two about it. 1st: The message overhead during communication is not an issue. It is tiny compared to the time it…
Or as simple as using the hardware accelerated CRC32 that we have in our x86 CPUs. Last time I checked, CRC32 worked surprisingly well as a hash.
Another bonus quirk, from the 486 and Pentium area.. BSWAP EAX converts from little endian to big endian and vice versa. It was a 32 bit instruction to begin with. However, we have the 0x66 prefix that switches between…
Nah, it is not that bad. Sure you can mess up your performance by picking bad compiler options, but most of the time you are fine with just default optimizations enabled and let it do it's thing. No need to understand…
Correct. And every graphic programmer worth it's salt had a copy of "Computer Graphics - Principles and Practice" on the desk and followed whatever came out of the "Graphics Gems" series. We knew about BSP, Octrees and…
In embedded, you often need message queues. A common way to implement these is to have an array of messages, sized for the worst case scenario and use this as the message pool. You keep the unused messages in a single…
> Linked lists are taught as fundamental data structures in programming courses, but they are more commonly encountered in tech interviews than in real-world projects. I beg to disagree. In kernels, drivers, and…
Hardware existed. Around 2006 I had some automotive entertainment system from NEC on my table which had one of the Bitboys GPU chips on it. Wrote some vector graphics API for it. It wasn't bad honestly. It supported…
I want this as a paint pigment please...
I wrote thousands lines of assembler for NASM. It was such a nice update to the good old turbo assembler back in the 90th.
It wasn't that bad. You had different memory models back then. If you wanted to keep things easy you just compiled for a memory model in which each pointer was either 16 bit (for code/data smaller than 64kb) or a memory…
Oh, nice.. I browsed a little through the code, and found that sort.com used self-modified to change the sorting order: ; note! jae is patched to a jbe if file is to be sorted in reverse! ; CODE_PATCH LABEL BYTE JAE…
> If you're dealing with very simple CPUs like the > ARM M0, sure. But even the M3/M4 allows unaligned > access. On ARM M3/M4 you have the same issue with LDRD and STRD instructions which do not allow unaligned access.…
> In hindsight maybe a binary level translator from 8080 to 8086 would have worked better (and be simple enough) Many programs written in assembly language used self modifying code back then. It saved RAM and improved…
Linux does not dragged down in performance by the thousands of virus and malware scanners.
ARM riding the "everything is AI" train. So sad.
Yea.. having fun with war.. Most American post I have seen here since ages.
The fun thing was the Roland Sync. You could sync up all the TB-303, TB-909 and all the others with a 5-pole DIN cable. The sync was badly implemented. It lagged, it had latency. However! As soon as you cabled all…
Easy, it is dopamine.
Back then Microsoft was lobbying as hard as they could to turn that decision to move to linux over. They knew: If Linux makes it in Munich, it will likely spread over and they loose tons of contracts with other German…
"I could only find a couple tutorials/guides and both were imperative" Aren't Quadtrees covered by almost all basic data-structure books? It is the most simple form of taking the binary tree into the next (2D) dimension.
this For those who don't know: Vias are not only used to get an electrical connection from one side of the PCB to another. You also need them to keep radiation in check and often to move heat away. With this technique,…
Honestly, this is really bad. It might be a breakthrough of what you are doing, but when I listen to the output all of the timing and phrasing is aweful.
There are couple of tricks you can do if you fiddle with the bits of a floating point value using integer arithmetic and binary logic. That was a thing back in the 90th.. I wonder how hard the performance hit from…
> 1. Apple having just announced it is opening up NFC > to developers means that both major mobile > platforms can now act as responding devices; > 2. Mobile consumer hardware is sufficiently fast for the application >…
I've worked in the payment industry and among other things built a payment terminal, so I know a thing or two about it. 1st: The message overhead during communication is not an issue. It is tiny compared to the time it…
Or as simple as using the hardware accelerated CRC32 that we have in our x86 CPUs. Last time I checked, CRC32 worked surprisingly well as a hash.
Another bonus quirk, from the 486 and Pentium area.. BSWAP EAX converts from little endian to big endian and vice versa. It was a 32 bit instruction to begin with. However, we have the 0x66 prefix that switches between…
Nah, it is not that bad. Sure you can mess up your performance by picking bad compiler options, but most of the time you are fine with just default optimizations enabled and let it do it's thing. No need to understand…
Correct. And every graphic programmer worth it's salt had a copy of "Computer Graphics - Principles and Practice" on the desk and followed whatever came out of the "Graphics Gems" series. We knew about BSP, Octrees and…
In embedded, you often need message queues. A common way to implement these is to have an array of messages, sized for the worst case scenario and use this as the message pool. You keep the unused messages in a single…
> Linked lists are taught as fundamental data structures in programming courses, but they are more commonly encountered in tech interviews than in real-world projects. I beg to disagree. In kernels, drivers, and…
Hardware existed. Around 2006 I had some automotive entertainment system from NEC on my table which had one of the Bitboys GPU chips on it. Wrote some vector graphics API for it. It wasn't bad honestly. It supported…
I want this as a paint pigment please...
I wrote thousands lines of assembler for NASM. It was such a nice update to the good old turbo assembler back in the 90th.
It wasn't that bad. You had different memory models back then. If you wanted to keep things easy you just compiled for a memory model in which each pointer was either 16 bit (for code/data smaller than 64kb) or a memory…
Oh, nice.. I browsed a little through the code, and found that sort.com used self-modified to change the sorting order: ; note! jae is patched to a jbe if file is to be sorted in reverse! ; CODE_PATCH LABEL BYTE JAE…
> If you're dealing with very simple CPUs like the > ARM M0, sure. But even the M3/M4 allows unaligned > access. On ARM M3/M4 you have the same issue with LDRD and STRD instructions which do not allow unaligned access.…