public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Grulich <jgrulich@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/qt6-qtwebengine] f45: Fix V8 build error
Date: Tue, 25 Aug 2026 06:25:33 GMT	[thread overview]
Message-ID: <178763913391.1.6913202921797989551.rpms-qt6-qtwebengine-3ed134173b0b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/qt6-qtwebengine
Branch : f45
Commit : 3ed134173b0b1cb29a8c984a99ece24b816f92b5
Author : Jan Grulich <jgrulich@redhat.com>
Date   : 2026-08-25T08:24:53+02:00
Stats  : +19/-0 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/qt6-qtwebengine/c/3ed134173b0b1cb29a8c984a99ece24b816f92b5?branch=f45

Log:
Fix V8 build error

---
diff --git a/qt6-qtwebengine.spec b/qt6-qtwebengine.spec
index 13c0998..32ba45c 100644
--- a/qt6-qtwebengine.spec
+++ b/qt6-qtwebengine.spec
@@ -137,6 +137,7 @@ Patch80:  qtwebengine-fix-arm-build.patch
 ## Upstreamable patches:
 Patch101: qtwebengine-fix-build-against-gcc16.patch
 Patch102: qtwebengine-fix-delay-signature.patch
+Patch103: qtwebengine-fix-v8-kMaximalBufferSize-private.patch
 
 ## ppc64le port
 Patch200: qtwebengine-6.9-ppc64.patch
@@ -498,6 +499,7 @@ popd
 ## upstreamable patches
 %patch -P101 -p1 -b .fix-build-against-gcc16
 %patch -P102 -p1 -b .fix-delay-signature
+%patch -P103 -p1 -b .fix-v8-kMaximalBufferSize-private
 
 # ppc64le support
 %patch -P200 -p1

diff --git a/qtwebengine-fix-v8-kMaximalBufferSize-private.patch b/qtwebengine-fix-v8-kMaximalBufferSize-private.patch
new file mode 100644
index 0000000..5e5d186
--- /dev/null
+++ b/qtwebengine-fix-v8-kMaximalBufferSize-private.patch
@@ -0,0 +1,17 @@
+diff --git a/src/3rdparty/chromium/v8/src/baseline/baseline-compiler.cc b/src/3rdparty/chromium/v8/src/baseline/baseline-compiler.cc
+--- a/src/3rdparty/chromium/v8/src/baseline/baseline-compiler.cc
++++ b/src/3rdparty/chromium/v8/src/baseline/baseline-compiler.cc
+@@ -275,11 +275,11 @@ std::unique_ptr<AssemblerBuffer> AllocateBuffer(
+   }
+   int raw_estimated_size;
+   if (!estimated_size.AssignIfValid(&raw_estimated_size) ||
+-      raw_estimated_size > Assembler::kMaximalBufferSize) {
++      raw_estimated_size > AssemblerBase::kMaximalBufferSize) {
+     V8::FatalProcessOutOfMemory(nullptr, "BaselineCompiler::AllocateBuffer");
+   }
+   int rounded_size = RoundUp(raw_estimated_size, 4 * KB);
+-  if (rounded_size > Assembler::kMaximalBufferSize) {
++  if (rounded_size > AssemblerBase::kMaximalBufferSize) {
+     V8::FatalProcessOutOfMemory(nullptr, "BaselineCompiler::AllocateBuffer");
+   }
+   return NewAssemblerBuffer(rounded_size);

                 reply	other threads:[~2026-08-25  6:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178763913391.1.6913202921797989551.rpms-qt6-qtwebengine-3ed134173b0b@fedoraproject.org \
    --to=jgrulich@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox