tree ba7ee95312f923f97870d84b96f5268c862959c8
parent ecb3eb3fdb9536472706c173d00b3379e3332469
author Alon Zakai <azakai@google.com> 1697662624 -0700
committer GitHub <noreply@github.com> 1697662624 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlMEagCRBK7hj4Ov3rIwAAvbYIADmzs+3SBVkcTFU9Oq3DPbZO
 0iZay2m3tKRwaKZZ+XYvNFIwPNPA6Xc1B+Gskul2eJB0i12ElFezEhQOQtlj88ak
 1voFpiMQc0nIzdEs6SUtfcag7MEyKDLgCxovd0fTRUsIfIfnerqcSIZmvNbhKR22
 TgAqCptOirEEeFaCT3DSiYh8wk3Q+/IRBglWgdZrjAYht6SpIplt0d5N8OxDy5bU
 UzpHBeX2oPKMuP2w2sYV56G3tnlzoa+LDnZ6zNjAu33+nDHkBs9DRjs4eF5dF+0w
 utRZorgpK7fybcrFH4l91IS5aZ17MWV6K8TpkEWO96RLivJs6ha2wcvtiy3cxBo=
 =uFwM
 -----END PGP SIGNATURE-----
 

SimplifyGlobals: Fold single-use globals to their use (#6023)

For example,

(global $a (struct.new $A))
(global $b (struct.new $B (global.get $A)))

=>

(global $b (struct.new $B (struct.new $A)))
and the global $a is now unused. This is valid if $a has no other uses.

This saves a little in code size, but should not really help otherwise, as we
already look through immutable global.get operations in important
optimizations. But the code size may matter if there are many such single-
use globals.