LowLevelMahn

PDBs can help alot

they (normaly) contain Source mapping: Links machine code addresses back to original source file names and line numbers.

Symbols: Lists names, addresses, and types for functions, global/local variables, and public exports.

Line numbers: Maps compiled instructions to specific source code lines.

and PDBs can exist also for Release builds but more pointing to a debug build - which in itself is way easier to reverse

no thats nearly impossible

be negative, no problem - the goal is different - we are foremost developers that like the challenge to get the game back into its source state - its interesting to see on an algorithmic level how the devs got it working at that time with all this hardcore constrains (It's like the joy of an archaeologist unearthing an old wooden tool.) - for many developers gaming was the startpoint of interest in software development, and reversing is the gold-class, all your life long expirience needs to be on point to be able to reach such a goal, maybe hard to understand for non-developers - and only a few people on the world are able to do that (even with LLMs) and developers praise these ones :)

its mostly the combined work of AJenbo, neuviemeporte and others - my part is very small, fixing some compilation problems with newer compilers and spreading the news

C source needs to get compiled on every platform reachable - that is a must :)

that is the inital post to explain what the link referes to...

the developer 'Wilczek' is posting the progress on his Railroad Tycoon reversing in this Vogons-Thread

this Rust demo also uses PTX directly

  During the build, build.rs uses rustc_codegen_nvvm to compile the GPU kernel to PTX.
  The resulting PTX is embedded into the CPU binary as static data.
  The host code is compiled normally.