4 ms·
There is serious abuse of nasm macro-preprocessor. Going to be tough to move away to another assembler.
by sylware 1y ago
There is serious abuse of nasm macro-preprocessor. Going to be tough to move away to another assembler.
- oguz-ismail 1y agoWhere? There's very little code in those lessons
- pveierland 1y agoThe lessons reference `cglobal` in `x86inc.asm`: https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x86inc.asm#L820 https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...
- loeg 1y agoWhy move away?
- saagarjha 1y agoNot everyone wants to use nasm. Sometimes all you have is the clang integrated assembler :(
- sylware 1y agoYou could use GAS, FASM2, or write an ffmpeg specific one: writting a real-life assembler is orders of magnitude simpler than writting a real-life compiler... Usually that implementation complexity is very dependent on the macro pre-precessor one. This is a matter of exit cost: for instance look at linux bitkeeper->git exit.
- sylware 1y agoYep, look at nasm SDK, horrible, with tons of perl generators, etc, etc. From the worst.
- loeg 1y ago> Not everyone wants to use nasm. Yeah, but I'd really only be concerned with what the ffmpeg developers want here.