On Fri May 16 20:26:42 2025 +0000, Yuxuan Shui wrote:
But note that it's actually an argument for keeping it as a separate
fork that you have the responsibility to maintain. That doesn't sound too bad actually. This is intended for developers anyway, so as long as devs are made aware and have easy access to this, it can be useful. maybe things will change in the future and this eventually get merged, but for now keeping it as a fork doesn't sound too bad.
Sadly that's not feasible without compiler support.
can you expand a bit on this? i am curious and do want to learn more. i know mingw has their crappy `__try1/__except1` macros, that doesn't quite work like the real `__try/__except`. is there something that prevents us from improving upon them?
also did a quick & crude survey on this, based on bernhardu's work, out of ~3.6M total lines of code, almost exactly 3M can be covered by PE ASan, so about 83.5%. out of those lines that can't be covered, 35.2% are unixlibs, the rest are DLLs that have to be exempted, presumably because they caused problems. (i excluded `libs`, and `tools`. comments and empty lines are not counted. obviously SLOC doesn't mean much, so this is more or less just for fun.).