runtime: investigate a hybrid memory clearing strategy based on prove results #57000
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Performance
Milestone
In some cases, it might be better/faster to have a hybrid memory clear where from prove we know that a clear will be at least X bytes long.
We could use a static clear and then handle the unknown-sized remainder (either via a call to memclrNoHeapPointers or some inlined clear for the remainder). This could improve performance or allow more optimizations to fire due to the static clear part enabling things like DSE.
The text was updated successfully, but these errors were encountered: