You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@davecheney noted in https://go-review.googlesource.com/#/c/20350/ that cmd/compile's binary size shrunk by about 400kB as a result of the CL. Investigating, it looks like this is mostly attributable to cmd/compile/internal/ppc64.varianttable:
Also, I note that table is sized for ppc64.ALAST, whereas it only needs to be sized for ppc64.ALAST & obj.AMask. Also, all of the progtables, and cmd/internal/obj/arm64's oprange table.
So all of those tables have a bunch of empty/unused space in them.
arm64's oprange is probably most worth fixing, because it actually contains pointers, so even if it's unused, the GC needs to scan it. (I think?)
The others waste disk space, but are pointer-free, so they shouldn't need to be paged in. Also, they're all zero values, so they should compress well in the binary distributions. (Still, probably worth fixing if someone wanted some easy low hanging fruit to look into.)
The text was updated successfully, but these errors were encountered:
@davecheney noted in https://go-review.googlesource.com/#/c/20350/ that cmd/compile's binary size shrunk by about 400kB as a result of the CL. Investigating, it looks like this is mostly attributable to cmd/compile/internal/ppc64.varianttable:
Also, I note that table is sized for ppc64.ALAST, whereas it only needs to be sized for ppc64.ALAST & obj.AMask. Also, all of the progtables, and cmd/internal/obj/arm64's oprange table.
So all of those tables have a bunch of empty/unused space in them.
arm64's oprange is probably most worth fixing, because it actually contains pointers, so even if it's unused, the GC needs to scan it. (I think?)
The others waste disk space, but are pointer-free, so they shouldn't need to be paged in. Also, they're all zero values, so they should compress well in the binary distributions. (Still, probably worth fixing if someone wanted some easy low hanging fruit to look into.)
The text was updated successfully, but these errors were encountered: