Compbinary format uses MD5 to represent strings in name table. That gives smaller profile. The patch adds the support in extbinary format. It is off by default but user can choose to enable it.
Note the feature of using MD5 in name table can bring very small chance of name conflict leading to profile mismatch. Besides, profile using the feature won't have the profile remapping support.
I thought SecFlags is a set of general purpose flags that can be applied to all section, at least SecFlagCompress falls under that category. For Name vs MD5Name, to some extended it's like section with different content. So would it make sense to have SecMD5NameTable in addition to SecNameTable for SecType, instead of relying on SecFlags? All reader/writer code can still be shared between the two.