Issue 1507690 in chromium: Unexpected static initializer count error in chrome/android:monochrome_static_initializers
1 view
Skip to first unread message
agrieve via monorail
Jan 8, 2024, 12:15:51 PMJan 8
to flag...@chromium.org
Updates:
Components: -UI>Browser>Mobile -Tools>StaticAnalysis Internals>Flags
Owner: ----
Status: Available
Comment #4 on issue 1507690 by agr...@google.com: Unexpected static initializer count error in chrome/android:monochrome_static_initializers
https://bugs.chromium.org/p/chromium/issues/detail?id=1507690#c4
From the build output, the new initializer was:
Disassembly of section .text:
0000000009008014 <_GLOBAL__sub_I_about_flags.cc>:
9008014: d503245f bti c
9008018: f00042c8 adrp x8, 0x9863000 <writev+0x9863000>
900801c: b0009229 adrp x9, 0xa24d000 <gwp_asan::internal::lud::SharedStateHolder<gwp_asan::internal::lud::RandomEvictionQuarantine>::buffer_+0x30>
9008020: 91342129 add x9, x9, #0xd08
9008024: f9451908 ldr x8, [x8, #0xa30]
9008028: b0fb8cca adrp x10, 0x1a1000 <alpha_lower_list+0x8f550>
900802c: 912de94a add x10, x10, #0xb7a
9008030: f9400508 ldr x8, [x8, #0x8]
9008034: a9002928 stp x8, x10, [x9]
9008038: 90fb936a adrp x10, 0x274000 <segmentation_platform::kAdaptiveToolbarUmaName+0x5090b>
900803c: 9137f94a add x10, x10, #0xdfe
9008040: a9012928 stp x8, x10, [x9, #0x10]
9008044: d0fb90ea adrp x10, 0x226000 <segmentation_platform::kAdaptiveToolbarUmaName+0x290b>
9008048: 911f954a add x10, x10, #0x7e5
900804c: a9022928 stp x8, x10, [x9, #0x20]
9008050: d65f03c0 ret
Not super helpful... We might get better output on a local build with symbol_level=2.
Nothing in the CL stands out to me as to why this flag would cause it when others do not.
We've at least updated android-binary-size trybot to check arm64 static initializer on CQ, so this kind of failure should be caught in CQ next time around.
Marking as available, as I think the checker is working fine. Might be a bug in the compiler, or in our flag macros... but I can't speak to either of those.
--
You received this message because:
1. You are auto-CC'd on all issues in component Internals>Flags
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment or make updates.
Components: -UI>Browser>Mobile -Tools>StaticAnalysis Internals>Flags
Owner: ----
Status: Available
Comment #4 on issue 1507690 by agr...@google.com: Unexpected static initializer count error in chrome/android:monochrome_static_initializers
https://bugs.chromium.org/p/chromium/issues/detail?id=1507690#c4
From the build output, the new initializer was:
Disassembly of section .text:
0000000009008014 <_GLOBAL__sub_I_about_flags.cc>:
9008014: d503245f bti c
9008018: f00042c8 adrp x8, 0x9863000 <writev+0x9863000>
900801c: b0009229 adrp x9, 0xa24d000 <gwp_asan::internal::lud::SharedStateHolder<gwp_asan::internal::lud::RandomEvictionQuarantine>::buffer_+0x30>
9008020: 91342129 add x9, x9, #0xd08
9008024: f9451908 ldr x8, [x8, #0xa30]
9008028: b0fb8cca adrp x10, 0x1a1000 <alpha_lower_list+0x8f550>
900802c: 912de94a add x10, x10, #0xb7a
9008030: f9400508 ldr x8, [x8, #0x8]
9008034: a9002928 stp x8, x10, [x9]
9008038: 90fb936a adrp x10, 0x274000 <segmentation_platform::kAdaptiveToolbarUmaName+0x5090b>
900803c: 9137f94a add x10, x10, #0xdfe
9008040: a9012928 stp x8, x10, [x9, #0x10]
9008044: d0fb90ea adrp x10, 0x226000 <segmentation_platform::kAdaptiveToolbarUmaName+0x290b>
9008048: 911f954a add x10, x10, #0x7e5
900804c: a9022928 stp x8, x10, [x9, #0x20]
9008050: d65f03c0 ret
Not super helpful... We might get better output on a local build with symbol_level=2.
Nothing in the CL stands out to me as to why this flag would cause it when others do not.
We've at least updated android-binary-size trybot to check arm64 static initializer on CQ, so this kind of failure should be caught in CQ next time around.
Marking as available, as I think the checker is working fine. Might be a bug in the compiler, or in our flag macros... but I can't speak to either of those.
--
You received this message because:
1. You are auto-CC'd on all issues in component Internals>Flags
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment or make updates.
Reply all
Reply to author
Forward
0 new messages