| commit | 1991342101e1af4947ca05cf3da08ea4228481bb | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Mon Mar 25 13:21:47 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 25 13:21:47 2024 |
| tree | 66ecf151abb8a609fbf61aa3b8179b60aa09c078 | |
| parent | ae5fb853bf7924bfbae1ffcb491d67804372e6ca [diff] |
Specify the underlying type for UMALinuxGlibcVersion enums are weird. They are neither limited to their listed values, but nor are they plain ints. If an enum is neither `enum class ...` nor `enum Foo : T`, its "underlying type" is not "fixed". In that case, although it is typically sized like an int, the range of values is defined by some bizarre "hypothetical integer type with minimal width" rule. https://eel.is/c++draft/dcl.dcl#dcl.enum-8 RecordLinuxGlibcVersion() specifically wants to store the full range of uint32_t in the enum, so just specify an underlying type of uint32_t. This fixes one of the two UBSan errors in this (and several other) test failures: https://luci-milo.appspot.com/ui/inv/build-8752555092756764593/test-results?q=All%2FAboutFlagsBrowserTest.ExpiryHidesFlag%2F0&sortby=&groupby= Bug: 40942951 Change-Id: Ic4c9d41d64be4a7e1fae53792a78a6469a07bc57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5390905 Reviewed-by: Erik Chen <erikchen@chromium.org> Auto-Submit: David Benjamin <davidben@chromium.org> Commit-Queue: David Benjamin <davidben@chromium.org> Cr-Commit-Position: refs/heads/main@{#1277593}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.