__cfstring is a special literal section, so instead of breaking it up
at symbol boundaries, we break it up at fixed-width boundaries (since
each literal is the same size). Symbols can only occur at one of those
boundaries, so this is strictly more powerful than
With that in place, we then run the section through ICF.
This change is about perf-neutral when linking chromium_framework.