Re: [v8-users] Reduce V8 size by eliminating unused features

2021-02-01 Thread Clemens Backes
Yep, the work to optionally strip out wasm is tracked in https://crbug.com/v8/11238. We have the gn arg now, but it does not reduce binary size yet. This will probably change until the end of this quarter. Follow the bug to get updates! On Mon, Feb 1, 2021 at 7:31 AM Jakob Gruber wrote: > +Cleme

Re: [v8-users] Reduce V8 size by eliminating unused features

2021-01-31 Thread Jakob Gruber
+Clemens Backes I know we'd discussed a flag to make wasm optional in the past, was there any progress? On Sat, Jan 30, 2021 at 11:48 AM Ben Noordhuis wrote: > On Fri, Jan 29, 2021 at 9:17 PM Tekman wrote: > > > > Hi, > > > > Do you have any tips for reducing the size of an embedded V8 by remo

Re: [v8-users] Reduce V8 size by eliminating unused features

2021-01-30 Thread Ben Noordhuis
On Fri, Jan 29, 2021 at 9:17 PM Tekman wrote: > > Hi, > > Do you have any tips for reducing the size of an embedded V8 by removing > unnecessary functionality (such as wasm or worker support)? Size on disk > comes to mind since I presume runtime cost is already pay-for-play. > > We're looking fo

[v8-users] Reduce V8 size by eliminating unused features

2021-01-29 Thread Tekman
Hi, Do you have any tips for reducing the size of an embedded V8 by removing unnecessary functionality (such as wasm or worker support)? Size on disk comes to mind since I presume runtime cost is already pay-for-play. We're looking for a basic ES6 runtime environment that is compact and effici