正在加载视频...

视频加载失败

Math is art. Machine instructions are an abstraction derived from mathematical operations at the hardware level. Assembly is a low-level representation of these instructions. Your C code compiles down to assembly, and Python was implemented in C. Learn the math.

18,693 次观看 • 1 年前 •via X (Twitter)

11 条评论

Fantasm Lister (mog/acc) 的头像
Fantasm Lister (mog/acc)1 年前

Amazing!

tetsuo.sol – mog/acc 的头像
tetsuo.sol – mog/acc1 年前

🤍

Matt Figdore 的头像
Matt Figdore2 年前

This is the biggest productivity cheat code right now. Kiss reading documents goodbye. You can get an instant summary of any document with this tool.

/̵͇̿̿/'̿'̿ ̿ ̿̿ ̿̿ ̿̿ ∑: 的头像
/̵͇̿̿/'̿'̿ ̿ ̿̿ ̿̿ ̿̿ ∑:1 年前

remilio

tetsuo.sol – mog/acc 的头像
tetsuo.sol – mog/acc1 年前

remilio

Aemilivs 的头像
Aemilivs1 年前

But... Machine instructions are specific implementations of mathematical operations, not abstractions derrived from them

tetsuo.sol – mog/acc 的头像
tetsuo.sol – mog/acc1 年前

yeah you're kind of right.

TRiM 的头像
TRiM1 年前

Everything is math..

@unknown 的头像
@unknown1 年前

This is strong

nathfavour🚀👨🏾‍💻 的头像
nathfavour🚀👨🏾‍💻1 年前

Learn the math 📍

🌠 的头像
🌠1 年前

@KefitzatHaderek

相关视频

FINALLY finishing up a MASSIVE PR from hell for the Sega Dreamcast port of Grand Theft Auto 3! This is an actual hardware capture now of the DC version under a high load, which would've previously been a slideshow, between the dynamic lighting from the sirens, the amount of rigid bodies in the physics simulation from the cars, and the high-speed chase placing high-demands on asset streaming... I went through all of the low-level common math infrastructure in both the engine and at the RenderWare driver layer and made numerous optimizations, before slowly working my way up to optimizing individual algorithms at the application layer using the new math routines. Firstly, the common low-level floating-point math routines for everything from trig and inverse square root operations to floor(), ceiling(), and clamp(), were replaced with what was meticulously found (in Compiler Explorer) to be the optimal patterns for GCC 14.2.0, targeting our SH architecture (sometimes favoring C builtins, sometimes inline SH4 ASM). Next, in the layer above, with inline SH4 assembly, the common matrix math and linear algebra routines were accelerated using the Dreamcast's vector instructions. Some cleverness went down here, such as cramming matrix metadata into unused insignificant bits of an element, combining loading two matrices with multiplying them, fast transposes, fast quaternion multiplication using 4 dot products, etc. Once the foundation was laid, some of the Renderware code such as the calculations for the lighting, updating bounding volumes, and deriving UV coordinates for specular environment maps on the cars was made faster automatically. The main gainz were actually made rewriting a decent amount of the collision intersection and contact resolution code, though, from using C++-style overloaded operators for multiplying single 4D vectors by a 4x4 matrix to doing batches of 4D vectors by the same matrix. This SUBSTANTIALLY reduced the number of times the backing 4x4 matrix bank had to be reloaded and allowed me to keep it resident within registers while it was being used by the intersection algorithms!

Falco Girgis

114,524 次观看 • 1 年前