ladybird/vcpkg.json
Timothy Flynn bfc9dc447f AK+LibWeb: Replace our home-grown base64 encoder/decoders with simdutf
We currently have 2 base64 coders: one in AK, another in LibWeb for a
"forgiving" implementation. ECMA-262 has an upcoming proposal which will
require a third implementation.

Instead, let's use the base64 implementation that is used by Node.js and
recommended by the upcoming proposal. It handles forgiving decoding as
well.

Our users of AK's implementation should be fine with the forgiving
implementation. The AK impl originally had naive forgiving behavior, but
that was removed solely for performance reasons.

Using http://mattmahoney.net/dc/enwik8.zip (100MB unzipped) as a test,
performance of our old home-grown implementations vs. the simdutf
implementation (on Linux x64):

                Encode    Decode
AK base64       0.226s    0.169s
LibWeb base64   N/A       1.244s
simdutf         0.161s    0.047s
2024-07-16 10:27:39 +02:00

91 lines
1.4 KiB
JSON

{
"builtin-baseline": "f7423ee180c4b7f40d43402c2feb3859161ef625",
"dependencies": [
{
"name": "fontconfig",
"platform": "linux | freebsd | openbsd"
},
"icu",
"libjpeg-turbo",
{
"name": "libpng",
"features": [
"apng"
]
},
{
"name": "libavif",
"features": [
"dav1d"
]
},
"simdutf",
{
"name": "skia",
"platform": "osx",
"features": [
"metal"
]
},
{
"name": "skia",
"platform": "linux | freebsd | openbsd",
"features": [
"vulkan"
]
},
{
"name": "skia",
"platform": "android"
},
"sqlite3",
{
"name": "vulkan",
"platform": "!android"
},
{
"name": "vulkan-headers",
"platform": "!android"
},
"woff2"
],
"overrides": [
{
"name": "fontconfig",
"version": "2.14.2#1"
},
{
"name": "icu",
"version": "74.2#2"
},
{
"name": "libjpeg-turbo",
"version": "3.0.2"
},
{
"name": "libpng",
"version": "1.6.43#1"
},
{
"name": "libavif",
"version": "1.0.4#1"
},
{
"name": "simdutf",
"version": "5.2.5#0"
},
{
"name": "skia",
"version": "124#0"
},
{
"name": "sqlite3",
"version": "3.45.3"
},
{
"name": "woff2",
"version": "1.0.2#4"
}
]
}