commit | 72f3015c3b8851749a6a0e0ea24d155dca15eca8 | [log] [tgz] |
---|---|---|
author | Nico Weber <thakis@chromium.org> | Tue Mar 24 15:45:15 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 24 15:45:15 2020 |
tree | d249e5a677a8f3cd9cf5dac142c52861ecf56370 | |
parent | 55c9c2ae93d7119e763315b7e355668fb34d373e [diff] |
Reland "Enable -Wunreachable-code in Chrome OS builds." This is a reland of 2ff5fdbc7071dbdd8bca67f3cb72cdcb636e543b with a build fix in code that's only built on some internal bot (it changes a FAIL() to an ADD_FAILURE() there, but the test still passes with that). Also enable on arm builds, since the fix for that has rolled in since the first attempt. Original change's description: > Enable -Wunreachable-code in (non-arm) Chrome OS builds. > > Bug: 1063529,346399 > Change-Id: I313ebf4cc16885d1f9bdc5a2ed8db524467735f2 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116590 > Commit-Queue: Ben Pastene <bpastene@chromium.org> > Reviewed-by: Ben Pastene <bpastene@chromium.org> > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Auto-Submit: Nico Weber <thakis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#752618} TBR=bpastene Bug: 1063529, 346399 Cq-Include-Trybots: chrome/try:linux-chromeos-chrome Change-Id: I1dd3cefcaa229b6e2655cee3cd20cf98f32be04b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116912 Reviewed-by: Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#752856}
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.
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.