On Thu Feb 20 16:23:15 2025 +0000, Paul Gofman wrote:
I am sorry, I am probably very late with this (although mentioned such a possibility a few days ago). I've made an ad-hoc test and observed that the module which is auto-loaded for GetProcAddress() on forwarded export makes the dependency loaded in the same DDAG node on Windows. So this looks like it directly interferes with what this series is trying to do. Shouldn't we implement it the same way (maybe even handling cyclic dependencies with DDAG node sharing aside)? Otherwise these complicated-looking changes might be moving this reference tracking in the wrong direction.
Uh, sorry, scratch that, I've got the test on Windows wrong with a missing dll... it is all right, it is loaded in a different node.