Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bazel: workaround invalid nonnull warning in v8 #23765

Merged
merged 1 commit into from
Nov 1, 2022
Merged

bazel: workaround invalid nonnull warning in v8 #23765

merged 1 commit into from
Nov 1, 2022

Commits on Oct 31, 2022

  1. bazel: workaround invalid nonnull warning in v8 

    Since gcc 12 it seems there are some false positives around this
warning.

Upstream gcc reports:

- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107252
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100366
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106199

We can't use `--per_file_copt` in this case because we build this in the
host configuration bazelbuild/bazel#12406

Upstream v8 report: https://bugs.chromium.org/p/v8/issues/detail?id=13441

Fixes envoyproxy#23692

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
    @keith
    keith committed Oct 31, 2022
    Configuration menu
    Copy the full SHA
    0a283ec View commit details
    Browse the repository at this point in the history