For 32-bit arm (LTO and non-LTO), ChromePublic.apk contains many symbols with prefix '.L_MergedGlobals', but should have more informative names.

To repro, build chrome_public_apk for arm (32-bit), then run:

  $ supersize archive -f ChromePublic.apk out.size
  ...
  $ supersize console out.size

  >>> size_info.raw_symbols.Filter(lambda s: s.full_name.startswith('.L_MergedGlobals'))

Non-LTO arm build has ~2300 such symbols, and ThinLTO arm build has ~2700.

These arise from the libchrome.so.map, which has entries like

 3002410  3002410       60     8         thinlto-cache/Thin-d899f7.tmp.o:(.bss..L_MergedGlobals.8)
 3002410  3002410       60     1                 .L_MergedGlobals.8
 3002410  3002410       20     1                 enterprise_management::_DevicePolicyResponse_default_instance_
 3002430  3002430       20     1                 enterprise_management::_TimePeriod_default_instance_
 3002450  3002450       20     1                 enterprise_management::_ActiveTimePeriod_default_instance_

Notice that '.L_MergedGlobals.8' masks the first named entry.

This does not happen for arm64, which can still use .L_MergedGlobals, but does not have the masking problem. Example:

         4e1c9c0          4e1c9c0       10     8         thinlto-cache/Thin-d2903d.tmp.o:(.bss..L_MergedGlobals)
         4e1c9c0          4e1c9c0        0     1                 $d.25
         4e1c9c0          4e1c9c0        8     1                 autofill::(anonymous namespace)::GetFilter()::filter
         4e1c9c8          4e1c9c8        8     1                 guard variable for autofill::(anonymous namespace)::GetFilter()::filter

Here, SuperSize ignores '$d.25', and correctly takes the first named symbol.