Debian Patches

Status for chromium/120.0.6099.224-1~deb11u1

Patch Description Author Forwarded Bugs Origin Last update
debianization/manpage.patch manpage updates/fixes Daniel Echeverry <epsilon77@gmail.com> yes
debianization/sandbox.patch debian specific instructions when no working sandbox is available Michael Gilbert <mgilbert@debian.org> no
debianization/master-preferences.patch search for {initial,master}_preferences in /etc/chromium
The default chromium behavior of checking the current binary directory for
initial_preferences or master_preferences doesn't conform to debian policy.
Andres Salomon <dilinger@debian.org> no
debianization/clang-version.patch hardcode lld for whatever version of clang we're using
Upstream doesn't allow overridding the linker name (other than toggling
lld vs gold).
Andres Salomon <dilinger@debian.org> no
fixes/ps-print.patch add postscript (ps) printing capability Salvatore Bonaccorso no
fixes/widevine-revision.patch set widevine version as undefined Michael Gilbert <mgilbert@debian.org> no
fixes/widevine-locations.patch try alternative locations for libwidevinecdm.so - $HOME/.local/lib/ (snap-friendly, see https://launchpad.net/bugs/1738149) Olivier Tilloy <olivier.tilloy@canonical.com> no
fixes/rust-clanglib.patch Rust adds some new clang dependencies; specifically:


This is in the libclang-rt-14-dev package, but with a different (and
architecture-specific) path. So we special-case linux instead of
doing the same thing that upstream does w/ chromeos.
Andres Salomon <dilinger@debian.org> no
fixes/material-utils.patch ./../third_party/material_color_utilities/src/cpp/palettes/tones.cc:59:27: note: use function 'std::abs' instead
double smallest_delta = abs(smallest_delta_hct.get_chroma() - chroma);
^~~
std::abs
../../third_party/material_color_utilities/src/cpp/palettes/tones.cc:70:9: error: use of undeclared identifier 'round'
if (round(chroma) == round(smallest_delta_hct.get_chroma())) {
^
no
fixes/perfetto.patch More simple build fixes needed by libstdc++-dev 13 Andres Salomon <dilinger@debian.org> no
fixes/blink-frags.patch More libstdc++13 build fixes. This should go upstream. no
fixes/v8-compressed-ptrs.patch Upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1487855

The upstream commit https://chromium-review.googlesource.com/c/v8/v8/+/4753150
introduced a build failure on armhf. I suspect this is what was intended,
but we'll see what upstream says.
Andres Salomon <dilinger@debian.org> no
fixes/atspi.patch https://chromium-review.googlesource.com/c/chromium/src/+/4883576 broke
builds with atspi >= 2.50. This fixes it.
Andres Salomon <dilinger@debian.org> no
fixes/absl-optional.patch work around a clang bug with libstdc++
Chromium 119 used absl's 'optional' implementation. Chromium 120 switched to
aliasing absl::optional to std::optional. In theory that should be all fine
and good, except for the fact that there's a bug in clang:

https://github.com/llvm/llvm-project/issues/50248

This bug is worked around in libc++, but not in libstdc++. There's (so far)
two types of errors we hit. The first is specifically with
absl::optional::emplace() -

>> gen/ui/gfx/x/randr.cc:482:13: error: no matching member function for call to 'emplace'
>> data.lc.emplace();
>> ~~~~~~~~^~~~~~~
>> /usr/bin/../lib/gcc/x86_64-linux-gnu/13/../../../../include/c++/13/optional:914:2: note: candidate template ignored: requirement 'is_constructible_v<x11::RandR::NotifyEvent::Lc>' was not satisfied [with _Args = <>]
>> emplace(_Args&&... __args)
>>

..and a similar error with just a few calls to absl::make_optional() -

>> ./../third_party/blink/renderer/core/loader/history_item.cc:185:19: error: no matching function for call to 'make_optional'
>> view_state_ = absl::make_optional<ViewState>();

We can't simply revert to using absl's optional implmentation, because a) they
are planning to remove it (<https://abseil.io/about/design/dropin-types>), and
b) chromium devs, having switched over and viewing absl::optional and
std::optional as aliases, play fast and loose with those namespace. We end up
playing an ever-worsening game of whack-a-mole trying to fix build errors which
are just inability to do implicit conversions.

Another option (which some other distributions have chosen to do) is to simply
switch to building against libc++. However, that means bundling a bunch more
libraries that build statically against libc++. That's undesirable.

This patch provides the option of providing a workaround for libstdc++. Instead
of using the official libstdc++ header for optional, we provide our own with
the is_constructible assertions removed. There's no logic changes, it just
removes an assertion we _know_ is met, but the compiler too broken to know it.

I just copied over /usr/include/c++/13/optional, and changed a few of the
functions (where you see an '#if 0' commenting out the original function).
We'll need to update this patch with major libstdc++ upgrades.

===================================================================
Andres Salomon <dilinger@debian.org> no
upstream/mojo.patch copy of missing files in content/test/data, taken from upstream git
This is just
cp chromium-git/content/test/data/*{html,mojom,js,ts} \
chromium-debian/content/test/data/

Upstream bug report about the missing files:
https://bugs.chromium.org/p/chromium/issues/detail?id=1293630
I'm not sure how much of them are actually needed, but it's easier to
just copy all of them for now. Hopefully this will be fixed upstream
shortly.

This copy is from chromium 120.0.6099.62.
no
upstream/nullptr_t.patch libstdc++13 build fixes; nullptr_t needs its namespace specified. Andres Salomon <dilinger@debian.org> no
upstream/string-include.patch Build fix for std::string usage in the header without including <string>. Andres Salomon <diliner@queued.net> no
disable/tests.patch no
disable/unrar.patch disable support for safe browsing inspection of rar files Andres Salomon <dilinger@debian.org> invalid upstream
disable/signin.patch disable browser sign-in no https://raw.githubusercontent.com/Eloston/ungoogled-chromium/master/resources/patches/ungoogled-chromium/disable-signin.patch
disable/android.patch disable dependency on chrome/android Michael Gilbert <mgilbert@debian.org> no
disable/catapult.patch remove dependencies on third_party catapult

See https://bugs.debian.org/922431 for more details, but tl;dr: we should
bring this back and just get rid of the (common) minified stuff in catapult/third_party/.

Stuff like chai, jszip, and node-d3 are packaged for debian already.
Michael Gilbert <mgilbert@debian.org> no
disable/font-tests.patch disable building font tests Michael Gilbert <mgilbert@debian.org> no
disable/swiftshader.patch avoid building the swiftshader library Michael Gilbert <mgilbert@debian.org> no
disable/swiftshader-2.patch additional swiftshader stuff exposed by official builds Andres Salomon <dilinger@debian.org> no
disable/google-api-warning.patch disable the google api key warning when those aren't found Michael Gilbert <mgilbert@debian.org> no
disable/third-party-cookies.patch disable third-party cookies by default
This is easily configured in
Settings -> Security & Privacy -> Cookies & other site data

With this patch, we just change the default on a new chromium profile.
Andres Salomon <dilinger@debian.org> no
disable/driver-chrome-path.patch Disable usage of google-chrome in driver Michel Le Bihan <michel@lebihan.pl> no
disable/widevine-cdm-cu.patch Disable Widevine CDM component updater Michel Le Bihan <michel@lebihan.pl> no
disable/angle-perftests.patch Disable ANGLE perftests Michel Le Bihan <michel@lebihan.pl> no
disable/clang-version-check.patch remove strict clang version check during config
Chromium 107 has a strict clang version check, added in commit
8f23a2c2d14fd799813134e995c160354d75d3a0. This needs a proper fix
upstream; some way to check (or specify) whether it's a distribution
build, and therefore shouldn't require a particular git version of
clang.

For now, let's just get this building in debian.
Andres Salomon <dilinger@debian.org> no
system/icu-shim.patch allow building against system icu even when is_offical_build=true
I noticed this when switching to an official build and trying to build against
the system's libicu, but it may be necessary for other system libs as well.
If we switch to using the bundled icu, we can see if it's possible to get rid
of it.
Andres Salomon <dilinger@debian.org> no
system/jpeg.patch use system jpeg library Michael Gilbert <mgilbert@debian.org> no
system/zlib.patch use system zlib library instead of embedded lzma in courgette Michael Gilbert <mgilbert@debian.org> no
system/event.patch use system libevent Michael Gilbert <mgilbert@debian.org> no
system/openjpeg.patch no
system/clang-format.patch no
system/opus.patch no
system/eu-strip.patch no
system/rapidjson.patch build against debian's rapidjson-dev package
Due to some questionable licensing (the JSON "do not use this for evil" license),
debian deletes all of third_party/angle/third_party/rapidjson even though a small
portion of it falls under that license. The library is tiny and doesn't change
much, so this lets chromium build against the system's rapidjson-dev header files.
Andres Salomon <dilinger@debian.org> no
system/rollup.patch include debian node libs (needed for rollup)
This is strictly just needed for bullseye's rollup , but may be useful
later on when we drop more nodejs stuff.

===================================================================
Andres Salomon <dilinger@debian.org> no
bookworm/clang16.patch This is some clang-18 stuff. For clang-16, the compiler chokes on these
flags. These used to only be enabled when llvm_force_head_revision=true,
but now they're enabled unconditionally.
Andres Salomon <dilinger@debian.org> no
bookworm/generate-ninja.patch Bookworm's older gn (generate-ninja) doesn't understand the "mnemonic"
variable. Since that string is used by tests that we delete, it doesn't
matter anyways.

===================================================================
Andres Salomon <dilinger@debian.org> no
bookworm/constcountrycode.patch Work around the following with libstdc++ 12:

./../components/autofill/core/browser/data_model/autofill_i18n_api.h:18:30: error: constexpr variable 'kLegacyHierarchyCountryCodeString' must be initialized by a constant expression
constexpr inline std::string kLegacyHierarchyCountryCodeString{"XX"};
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

===================================================================
Andres Salomon <dilinger@debian.org> no
bullseye/disable-mojo-ipcz.patch disable kMojoIpcz to fix trap runtime error on i386
See https://bugs.debian.org/1034406
Andres Salomon <dilinger@debian.org> no
bullseye/webui.patch work around build failure with optimize_webui enabled on bullseye
Can be dropped post-bullseye.
Andres Salomon <dilinger@debian.org> no
bullseye/openh264.patch disable support for openh264, will be added later Michael Gilbert <mgilbert@debian.org> no
bullseye/av1-vaapi.patch Bullseye's libva-dev is too old, and doesn't support av1 encoding. So (partially)
revert the patch that ties it into encode accelerator
(1c1502a0cbc69465e2dc8b2a6d0c0fb7213376b4), and don't build the av1 vaapi encoder
that was added with chromium 114.
Andres Salomon <dilinger@debian.org> no
bullseye/av1-vaapi2.patch In order to fix:
../../media/gpu/vaapi/vaapi_wrapper.cc:3133:17: error: use of undeclared identifier 'VAConfigAttribEncAV1Ext1'; did you mean 'VAConfigAttribEncJPEG'?

This is a revert of:


commit eb35ad8a45c851887decf7b753600b7d48c087b7

media/gpu: Add cyclic refresh support for hardware AV1 encoding

Add cyclic refresh (AQ mode 3) support for hardware AV1 encoding.

VideoEncoderTest.MeasureProducedBitstreamQuality
PSNR Average
Before
180p: 37.8432dB
360p: 39.5612dB
720p: 40.3080dB

After
180p: 38.0221dB
360p: 40.0368dB
720p: 41.0902dB



VideoEncoderTest.MeasureProducedBitstreamQuality
Bitrate Deviation
Before
180p: 0.55%
360p: 0.10%
720p: -0.07%

After
180p: -0.51%
360p: -0.01%
720p: 0.03%



VideoEncoderTest.MeasureUncappedPerformance
Bitstream encode time average
Before
180p: 1.29832ms
360p: 1.8383ms
720p: 2.9665ms

After
180p: 1.28287ms
360p: 2.17763ms
720p: 3.81374ms

Bug: b/274756117
Test: Tested using video_encode_accelerator_perf_tests on Rex.

Change-Id: I2af5e40b9bae6d59b2e337edd47673603b45b766
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4784030
Commit-Queue: Justin Green <greenjustin@google.com>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1201526}

===================================================================
Justin Green <greenjustin@google.com> no 2023-09-26
bullseye/downgrade-typescript.patch This reverts the following commit:





commit 98d9d46d28f823d436b16018c15bdc9c9f7f6061

Upgrade TypeScript to 5.1.3

DISABLE_THIRD_PARTY_CHECK=TS upgrade and source code changes.

Bug: none
Change-Id: I21244e75a24e8e323ef40c696254e552f3956e6d
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4583215
Reviewed-by: Simon Znd <szuend@chromium.org>
Commit-Queue: Jack Franklin <jacktfranklin@chromium.org>

===================================================================
Jack Franklin <jacktfranklin@google.com> no 2023-06-02
bullseye/lerp.patch ../../chrome/browser/ui/views/tabs/tab_style_views.cc:490:10: error: call to 'lerp' is ambiguous
return std::lerp(static_cast<float>(base_opacity), GetHoverOpacity(), GetHoverAnimationValue());
^~~~~~~~~
/usr/bin/../lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/cmath:1911:3: note: candidate function
lerp(float __a, float __b, float __t) noexcept
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/cmath:1915:3: note: candidate function
lerp(double __a, double __b, double __t) noexcept
^
1 error generated.
no
bullseye/devtools-ts-return.patch Fix the following build error:
../../third_party/devtools-frontend/src/front_end/entrypoints/formatter_worker/JavaScriptFormatter.ts(94,42): error TS7030: Not all code paths return a value.

https://chromium.googlesource.com/devtools/devtools-frontend/+/4164e91fa6444c988d56d85bd3314def5fde5c98%5E%21/
https://crbug.com/1477210

This is the commit that broke it. I *think* that return is benign, and was
simply included because older typescript needed it. But we're still using
an older typescript (see bullseye/downgrade-typescript.patch), so we need it.


===================================================================
Andres Salomon <dilinger@debian.org> no
bullseye/pathmax.patch PATH_MAX needs limits.h

===================================================================
Andres Salomon <dilinger@debian.org> no
bullseye/framesensorconst.patch ../../content/browser/generic_sensor/frame_sensor_provider_proxy.cc:24:1: error: constexpr function's return type 'std::vector<blink::mojom::PermissionsPolicyFeature>' is not a literal type
SensorTypeToPermissionsPolicyFeatures(SensorType type) {
^
/usr/bin/../lib/gcc/x86_64-linux-gnu/10/../../../../include/c++/10/bits/stl_vector.h:389:11: note: 'vector<blink::mojom::PermissionsPolicyFeature>' is not literal because it is not an aggregate and has no constexpr constructors other than copy or move constructors
class vector : protected _Vector_base<_Tp, _Alloc>
^
1 error generated.

===================================================================
Andres Salomon <dilinger@debian.org> no
bullseye/node-trustedtypes.patch This reverts the following commit, plus adds like 20 more workarounds in
various other places. Necessary for our older typescript.



commit 63d6d3edb0bb9481e21ac2ae90893c88564615bd

WebUI: Remove remaining innerHTML 'as unknown as string' casts.

This type cast is no longer necessary after adding a workaround for [1]
in third_party/node/node_modules/typescript at crrev.com/c/3970137.

[1] https://github.com/microsoft/TypeScript/issues/30024

Bug: 1098690
Change-Id: I990822c645cba1416ba9096a65eaa527350bb30e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3972236
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1062442}

===================================================================
dpapad <dpapad@chromium.org> no 2022-10-22
ungoogled/disable-web-environment-integrity.patch no
ungoogled/disable-privacy-sandbox.patch disable Privacy Sandbox completely
https://github.com/ungoogled-software/ungoogled-chromium/blob/master/patches/core/ungoogled-chromium/disable-privacy-sandbox.patch
no
i386/support-i386.patch don't disable i386 builds on linux
https://chromium-review.googlesource.com/c/chromium/src/+/3583780

Chromium upstream decided to kill off i386 builds on Linux. They were
goin to add a 'force_x86_support' arg, but instead "[distributions that
still support i386] can patch the file."

At this point, i386 on linux is completely unsupported upstream, so
we're on our own with bugs.
Andres Salomon <dilinger@debian.org> no
i386/angle-lockfree.patch revert compile-time lockfree check; switch back to a runtime check.
This reverts the following:

"commit ce8ce6f81eff8a84e2ea59930cb995b1107181e2 (origin/chromium/5572)

Remove ASSERT from AtomicSerial, use static_assert

ASSERT is not constexpr, while the AtomicSerial constructor was.
This would cause compile errors.

Bug: angleproject:7989
Change-Id: Ib6a438d4c055378d4f2f667285b0d2e99f2522ad
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/4205892
"

The problem is that this is a compile-time check to ensure that a std::atomic<uint64_t>
doesn't require a mutex, but for i386 we can't guarantee that; instead, i386 checks
at runtime for the relevant CPU instructions. So we need to revert back to a runtime
assertion.

Since this is in ANGLE rather than Chromium, hopefully there's a chance they'll take a
fix upstream; probably a revert combined with dropping the "constexpr".
Kimmo Kinnunen <kkinnunen@apple.com> no 2023-01-31
ppc64le/sandbox/0001-linux-seccomp-bpf-ppc64-glibc-workaround-in-SIGSYS-h.patch [PATCH] linux/seccomp-bpf: ppc64+glibc workaround in SIGSYS handler
Workaround for an apparent issue with glibc negating syscall
parameters. Observed on a ppc64le machine with glibc.
More investigation required.
Shawn Anastasio <shawn@anastas.io> no 2019-01-15
ppc64le/sandbox/0001-sandbox-Enable-seccomp_bpf-for-ppc64.patch [PATCH 1/1] sandbox: Enable seccomp_bpf for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0001-services-service_manager-sandbox-linux-Fix-TCGETS-de.patch [PATCH] services/service_manager/sandbox/linux: Fix TCGETS declaration on PPC64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-10
ppc64le/sandbox/0001-sandbox-linux-bpf_dsl-Update-syscall-ranges-for-ppc6.patch [PATCH 1/4] sandbox/linux/bpf_dsl: Update syscall ranges for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0001-sandbox-linux-Implement-partial-support-for-ppc64-sy.patch [PATCH] sandbox/linux: Implement partial support for ppc64 syscalls and ucontext

Unlike other architectures, the ppc64 files currently rely on applicable
headers being provided by the system. It is sufficient for standard
GNU/Linux environments, but may require expansion elsewhere.
Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0001-sandbox-linux-Update-IsSyscallAllowed-in-broker_proc.patch [PATCH] sandbox/linux: Update IsSyscallAllowed in broker_process.cc Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-10-23
ppc64le/sandbox/0001-sandbox-linux-Update-syscall-helpers-lists-for-ppc64.patch [PATCH] sandbox/linux: Update syscall helpers/lists for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-09-18
ppc64le/sandbox/0002-sandbox-linux-bpf_dsl-Modify-seccomp_macros-to-add-s.patch [PATCH 1/4] sandbox/linux/bpf_dsl: Modify seccomp_macros to add support for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0003-sandbox-linux-system_headers-Update-linux-seccomp-he.patch [PATCH 3/4] sandbox/linux/system_headers: Update linux seccomp header for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0004-sandbox-linux-system_headers-Update-linux-signal-hea.patch [PATCH 4/4] sandbox/linux/system_headers: Update linux signal header for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0005-sandbox-linux-seccomp-bpf-Add-ppc64-syscall-stub.patch [PATCH] sandbox/linux/seccomp-bpf: Add ppc64 syscall stub Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-09
ppc64le/sandbox/0005-sandbox-linux-update-unit-test-for-ppc64.patch [PATCH 5/6] sandbox/linux: update unit test for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-09-13
ppc64le/sandbox/0006-sandbox-linux-disable-timedwait-time64-ppc64.patch =================================================================== no
ppc64le/sandbox/0007-sandbox-linux-add-ppc64-stat.patch =================================================================== no
ppc64le/sandbox/Sandbox-linux-services-credentials.cc-PPC.patch =================================================================== no
ppc64le/sandbox/0008-sandbox-fix-ppc64le-glibc234.patch =================================================================== no
ppc64le/third_party/0001-third_party-angle-Include-missing-header-cstddef-in-.patch =================================================================== no
ppc64le/third_party/0001-Add-PPC64-support-for-boringssl.patch =================================================================== no
ppc64le/third_party/0001-third_party-libvpx-Properly-generate-gni-on-ppc64.patch [PATCH] third_party/libvpx: Properly generate gni on ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-09-04
ppc64le/third_party/0001-third_party-lss-Don-t-look-for-mmap2-on-ppc64.patch =================================================================== no
ppc64le/third_party/0001-third_party-pffft-Include-altivec.h-on-ppc64-with-SI.patch [PATCH] third_party/pffft: Include altivec.h on ppc64 with SIMD enabled Shawn Anastasio <shawn@anastas.io> no 2019-04-24
ppc64le/third_party/0002-third_party-lss-kernel-structs.patch =================================================================== no
ppc64le/webrtc/Rtc_base-system-arch.h-PPC.patch =================================================================== no
ppc64le/crashpad/0002-Include-cstddef-to-fix-build.patch [PATCH] Include cstddef to fix build
size_t is not defined unless cstddef is included.
Timothy Pearson <tpearson@raptorengineering.com> no 2018-08-30
ppc64le/third_party/0004-third_party-crashpad-port-curl-transport-ppc64.patch =================================================================== no
ppc64le/workarounds/HACK-third_party-libvpx-use-generic-gnu.patch =================================================================== no
ppc64le/workarounds/HACK-debian-clang-disable-skia-musttail.patch =================================================================== no
ppc64le/libaom/0001-Add-ppc64-target-to-libaom.patch [PATCH] Add ppc64 target to libaom Shawn Anastasio <shawnanastasio@gmail.com> no 2019-03-10
ppc64le/libaom/0001-Add-pregenerated-config-for-libaom-on-ppc64.patch =================================================================== no
ppc64le/third_party/0002-third_party-libvpx-Remove-bad-ppc64-config.patch =================================================================== no
ppc64le/third_party/0002-third-party-boringssl-add-generated-files.patch =================================================================== no
ppc64le/third_party/0003-third_party-libvpx-Add-ppc64-generated-config.patch =================================================================== no
ppc64le/third_party/0003-third_party-ffmpeg-Add-ppc64-generated-config.patch =================================================================== no
ppc64le/third_party/0004-third_party-libvpx-work-around-ambiguous-vsx.patch =================================================================== no
ppc64le/third_party/skia-vsx-instructions.patch =================================================================== no
ppc64le/ffmpeg/0001-Add-support-for-ppc64.patch [PATCH] Add support for ppc64 Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-09-01
ppc64le/breakpad/0001-Implement-support-for-ppc64-on-Linux.patch [PATCH] Implement support for ppc64 on Linux
This patch implements support for the ppc64 architecture on Linux systems.

Notable changes include:
* Modification of tests to support non-4K page sizes
* minidump_writer: Determine size of stack to capture based on page size
* dump_writer_common: Introduce member function GetVectorRegisters to
ThreadInfo on ppc64 systems. This allows Altivec/VMX registers to be
dumped like they are on OS X. linux_ptrace_dumper has been updated
to utilize this function along with the ptrace mode NT_PPC_VMX.
* processor/exploitability_unittest.cc: Tests were disabled on
non-x86 systems. They assume the system objdump is capable of
disassembling x86 binaries which is not the case on other
architectures.

To-do:
* tools/linux/md2core has been updated as well, but functionality
has not been confirmed and restoration of Altivec/VMX registers
has not been implemented

Note that proper functionality depends on updates to third_party/LSS
that introduce PPC64 support. An in-progress patch that allows
breakpad to build and run successfully is available at:
https://wiki.raptorcs.com/wiki/Porting/Chromium
Shawn Anastasio <shawnanastasio@yahoo.com> no 2018-08-17
ppc64le/crashpad/0001-Implement-support-for-PPC64-on-Linux.patch [PATCH] Implement support for PPC64 on Linux
This patch implements support for the PPC64 architecture on Linux hosts.
Shawn Anastasio <sanastasio@raptorengineering.com> no 2018-08-30
ppc64le/database/0001-Properly-detect-little-endian-PPC64-systems.patch =================================================================== no
ppc64le/third_party/0001-Force-baseline-POWER8-AltiVec-VSX-CPU-features-when-.patch [PATCH] Force baseline POWER8 / AltiVec / VSX CPU features when on a PPC64 platform in LE mode Timothy Pearson <tpearson@raptorengineering.com> no 2018-09-21
ppc64le/fixes/fix-breakpad-compile.patch =================================================================== no
ppc64le/fixes/fix-partition-alloc-compile.patch ===================================================================
===================================================================
no
ppc64le/v8/0002-Add-ppc64-trap-instructions.patch =================================================================== no
ppc64le/third_party/0001-Fix-highway-ppc-hwcap.patch =================================================================== no
ppc64le/third_party/0001-Add-PPC64-support-for-libdav1d.patch [PATCH] Add PPC64 support for libdav1d Colin Samples <colin.samples+git@gmail.com> no 2019-11-01
ppc64le/third_party/0001-Fix-libdav1d-compilation-on-clang-ppc.patch [PATCH] Fix libdav1d compilation on clang ppc Colin Samples <colin.samples+git@gmail.com> no 2019-12-08
ppc64le/sandbox/fix-ppc64-linux-syscalls-headers.patch =================================================================== no
ppc64le/third_party/0003-thirdparty-fix-dav1d-gn.patch =================================================================== no
ppc64le/third_party/use-sysconf-page-size-on-ppc64.patch =================================================================== no
ppc64le/third_party/dawn-fix-typos.patch =================================================================== no
ppc64le/third_party/dawn-fix-ppc64le-detection.patch =================================================================== no
ppc64le/fixes/fix-unknown-warning-option-messages.diff =================================================================== no
ppc64le/third_party/0002-Highway-disable-128-bit-vsx.patch =================================================================== no

All known versions for source package 'chromium'

Links