In D73739 @MaskRay pointed out that the lengths for CallSiteRanges in .gcc_except_table are not quite correct if blocks are outlined or using basic-block-sections. At runtime this is fine because the .eh_frame data will limit a function to a particular LSDA entry so that even though the longer length allows buffer-overflow the code length in .eh_frame acts as a back-stop.
However, in post-binary analysis tools (e.g. BOLT) that may only parse the .gcc_except_table section having these lengths be incorrect will result in a buffer overflow when using this field to read forward.
There's no binary cost for making these labels correct and leads to smaller offsets which compress better leading to very minor metadata size reduction.