From 9a9c92814f4cdfb6c0e0ea64de80dd6fc6768354 Mon Sep 17 00:00:00 2001 From: TBK Date: Fri, 28 Feb 2020 17:39:48 +0100 Subject: community/chromium: upgrade to 80.0.3987.122 --- community/chromium/gcc-fno-delete-null-pointer-checks.patch | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'community/chromium/gcc-fno-delete-null-pointer-checks.patch') diff --git a/community/chromium/gcc-fno-delete-null-pointer-checks.patch b/community/chromium/gcc-fno-delete-null-pointer-checks.patch index 792cef60f6..55118fef27 100644 --- a/community/chromium/gcc-fno-delete-null-pointer-checks.patch +++ b/community/chromium/gcc-fno-delete-null-pointer-checks.patch @@ -1,17 +1,15 @@ -diff --git a/v8/BUILD.gn b/v8/BUILD.gn -index 3c03942..870b1e6 100644 --- ./v8/BUILD.gn +++ ./v8/BUILD.gn -@@ -577,6 +577,14 @@ config("toolchain") { - defines += [ "V8_ANDROID_LOG_STDOUT" ] +@@ -675,6 +675,14 @@ + defines += [ "V8_TARGET_OS_WIN" ] } + if (!is_win && !is_clang) { -+ # GCC 6+ can optimize away pointer comparisons to null. This is ++ # GCC 6 can optimize away pointer comparisons to null. This is + # problematic as V8 encodes Values through tagged pointers and comparisons + # with 0 are actually necessary in many cases. As a temporary Workaround + # we disable this optimization. See: https://crbug.com/v8/3782 -+ cflags += [ "-fno-delete-null-pointer-checks" ] ++ cflags = [ "-fno-delete-null-pointer-checks" ] + } + # TODO(jochen): Support v8_enable_prof on Windows. -- cgit v1.2.3