Closed hoodmane closed 14 hours ago
Well it's going to conflict with #22998, I suppose you can pick which one to merge first.
Can you confirm those codesize changes are all due to this change? i.e. can you run the rebase on main
and confirm you don't see any changes?
There are a lot of similar changes when I run it on main too.
There are a lot of similar changes when I run it on main too.
Maybe try with emsdk install tot
(or otherwise make sure you have the latest llvm and binaryen). (Also try ./emcc --clear-cache
)
Even after ./emsdk install tot
, and clearing cache and getting the most up to date main branch I get a bunch of changes from the rebaseline.
Even after
./emsdk install tot
, and clearing cache and getting the most up to date main branch I get a bunch of changes from the rebaseline.
Hmm.. that is strange/annoying. Maybe just revert those files then, and I can do a rebaseline after this lands.
OK, I just pushed another rebaseline commit, perhaps this one will match what you are generated on main now?
Nope, even if I check out your rebaseline commit and do a clean install of tot from emsdk I get a bunch of changes in code size by one to ten bytes.
I think this PR fixes the case when you symlink a directory to itself symlink(".", "dir")
and then try to glob("**")
it. The previous lookupPath
doesn't seem to detect this loop.
@sbc100 can this be merged?
This removes the recursion from
lookupPath
and in my opinion makes the control flow much more explicit and comprehensible.