News for hackers. Stuff that matters.
Re:FFmpeg School of Assembly Language by MortyWaves on Sunday February 23, 2025 @05:39AM (#43148345)
Doesn’t this just make it harder to maintain ports to other architectures though?
Re:FFmpeg School of Assembly Language by epr on Sunday February 23, 2025 @07:11AM (#43148724)
For what's written in assembly, lack of portability is a given. The only exceptions would presumably be high level entry points called to from C, etc. If you wanted to support multiple targets, you have completely separate assembly modules for each architecture at least. You'd even need to bifurcate further for each simd generation (within x64 for example).
Re:FFmpeg School of Assembly Language by antoinealb on Sunday February 23, 2025 @06:25AM (#43148539)
Yes, but on projects like that, ease of maintenance is a secondary priority when compared to performance or throughput.
Re:FFmpeg School of Assembly Language by secondcoming on Sunday February 23, 2025 @06:27AM (#43148545)
SIMD instructions are already architecture dependent
Re:FFmpeg School of Assembly Language by wolf550e on Sunday February 23, 2025 @11:03AM (#43150221)
There indeed have been bugs caused by amd64 assembly code assuming unix calling convention being used for Windows builds and causing data corruption. You have to be careful.