[v8-users] Re: The V8 JS language launch process is deprecated, use Blink Intents instead

other Web Platform APIs or modifications to Chromium), TAG review is recommended." The docs were updated accordingly. Cheers, Michael *From: *Michael Hablich *Date: *Thu, Apr 25, 2019 at 4:22 PM *To: *Michael Hablich Hablich *Cc: *Adam Klein, , Hi folks, > as of now, please do not use

[v8-users] The V8 JS language launch process is deprecated, use Blink Intents instead

Hi folks, as of now, please do not use the old V8 JS language launch process for launching new JS features. *Please use the Blink intent process instead, if you want to develop WebAssembly and JavaScript language features*. More information and details can be found here

[v8-users] Re: Branch cut V8 7.5

. In that case please apply the label Merge-Requested-7.5 to the bug the CL is fixing. See https://v8.dev/docs/merge-patch for more information on merging. Thanks, Michael On Thu, Apr 11, 2019 at 5:39 PM Michael Hablich wrote: > Hi, > > it is time again. If you have any questions regarding th

[v8-users] Branch cut V8 7.5

Hi, it is time again. If you have any questions regarding the release, please ping this thread. *THURSDAY 2019-04-11: API adoption freeze starting* V8 will branch in one week for the upcoming Beta phase for Chrome 75. On the 2019-04-18 one of the latest Canaries will be selected to be the branch

[v8-users] Re: Branch cut V8 7.4

, Michael On Thu, Feb 28, 2019 at 12:41 PM Michael Hablich wrote: > Hi, > > it is time again. If you have any questions regarding the release, please > ping this thread. > > THURSDAY 2019-02-28: API adoption freeze starting > V8 will branch in one week for the upcoming Bet

[v8-users] Branch cut V8 7.4

Hi, it is time again. If you have any questions regarding the release, please ping this thread. THURSDAY 2019-02-28: API adoption freeze starting V8 will branch in one week for the upcoming Beta phase for Chrome 74. On the 2019-03-07 one of the latest Canaries will be selected to be the branch

[v8-users] Re: Looking for people to maintain the MIPS port

Hi, there was no response to this thread and other outreach at all, so we will go ahead and remove the MIPS(64) ports from V8 starting with V8 7.5 (~mid March). Cheers, Michael +v8-mips-ports On Mon, Feb 4, 2019 at 11:30 AM Michael Hablich wrote: > Hi, > > we thank RT-RK and Wave

[v8-users] Looking for people to maintain the MIPS port

Hi, we thank RT-RK and Wave Computing for the yearlong work on V8's MIPS port. Unfortunately Wave Computing is no longer sponsoring V8's MIPS port, thus RT-RK cannot continue working on it. This means that we are now looking for entities that are willing to maintain the port instead. If you are

[v8-users] Branch cut V8 7.3

Hi, we have officially branched to be prepared for the upcoming Chrome version 70. The base of the branch is currently rolled into Chromium. It is based on one of the latest Chrome Canaries. *Integration into Chromium is stopped until Chromium has branched too.* V8 branch: branch-heads/7.3

[v8-users] Re: Branch cut V8 7.2

hing for more information on merging. Thanks, Michael On Thu, Nov 22, 2018 at 12:11 PM Michael Hablich wrote: > Hi, > > it is time again. If you have any questions regarding the release, please > ping this thread. > > THURSDAY 2018-11-22: API adoption freeze starting > V

[v8-users] Branch cut V8 7.2

Hi, it is time again. If you have any questions regarding the release, please ping this thread. THURSDAY 2018-11-22: API adoption freeze starting V8 will branch in one week for the upcoming Beta phase for Chrome 72. On the 2018-11-29 one of the latest Canaries will be selected to be the branch

[v8-users] Re: Branch cut V8 7.1

is fixing. See https://github.com/v8/v8/wiki/Merging%20&%20Patching for more information on merging. Thanks, Michael On Thu, Oct 4, 2018 at 2:12 PM Michael Hablich wrote: > Hi, > > it is time again. If you have any questions regarding the release, please > ping this thread. > &g

[v8-users] Branch cut V8 7.1

Hi, it is time again. If you have any questions regarding the release, please ping this thread. THURSDAY 2018-10-04: API adoption freeze starting V8 will branch in one week for the upcoming Beta phase for Chrome 71. On the 2018-10-11 one of the latest Canaries will be selected to be the branch

Re: [v8-users] Arraybuffer

Hi Dan, as already pointed out in this thread and other ones created by you: Please ask blink-related questions on blink-...@chromium.org. A good way to understand how something works is to check existing code as Caitlin already pointed out. Please use cs.chromium.org for this. If *after*

[v8-users] Branch cut V8 7.0

Hi, it is time again. If you have any questions regarding the release, please ping this thread. THURSDAY 2018-08-23: API adoption freeze starting V8 will branch in one week for the upcoming Beta phase for Chrome 70. On the 2018-08-30 one of the latest Canaries will be selected to be the branch

[v8-users] Changes to the V8 API changes doc

Hi folks, *you can stop reading now if you don't know what the 'V8 API changes ' doc is :-).* We are no longer planning on adding a list of changes to the V8 API in the 'V8 API changes

Re: [v8-users] I can not build the V8

ocess.CalledProcessError: Command '['/usr/bin/python', '-u', > 'tools/mb/mb.py', 'gen', '-f', 'infra/mb/mb_config.pyl', '-m', > 'developer_default', '-b', 'x64.release', 'out.gn/x64.release']' returned > non-zero exit status 1 > > Do you have a thought ? > thanks for the help > > >

Re: [v8-users] I can not build the V8

Do the steps in https://github.com/v8/v8/wiki/Building-from-Source work for you? On Wed, Jul 26, 2017 at 11:37 AM Ross SimbioS wrote: > Hi. > Please help me. > My problem: > > root@server:/opt/v8/tools/dev# ./v8gen.py -vv x64.release > >

[v8-users] PSA: V8 is going to switch to a new compiler architecture after 5.8 branch cut

Summary The V8 team is currently working on a new compiler pipeline that will help us bring future speedups to real-world JavaScript . In the next few weeks we will replace our current compiler architecture based

[v8-users] How to try out the future configuration of V8

Hi, you probably already have read it on Twitter or the V8 blog : V8 is going to switch to a new compiler architecture in the next few months. We are planning to deprecate FullCodeGen+Crankshaft in favor of

[v8-users] Re: ES2015 module support?

There is already a flag: --harmony-modules. As you can see in the tracking bug, there is a lot of development work going on. The feature also needs support in the embedders to work correctly, which was/is unspecified currently. On Saturday, January 7, 2017 at 11:18:20 PM UTC+1, Owen Densmore

[v8-users] Re: Disabling All Of The Optimizations

--no-crankshaft should do the trick. The name is misleading, it will also disable TurboFan. On Tuesday, September 20, 2016 at 1:51:51 PM UTC+2, PhistucK wrote: > > I have an issue where the code suddenly (since Chrome 53) gets caught up > in a cyclic recursion until it exceeds the stack size

[v8-users] Re: Try-Catch optimization in Turbofan

tion so it does not inline them again. > Having this optimization ship will mean one less thing to worry about when > writing code. > > Thanks! > -Ali > On Monday, July 18, 2016 at 7:55:17 AM UTC-7, Michael Hablich wrote: >> >> What is the reason the optimization

Re: [v8-users] Re: v8 Issue Tracker Migration

And to clarify further: There is no 'old issue list'. The issue IDs are still valid. So if you can't find the issue on Monorail it also never existed in our old tracker. On Thursday, March 10, 2016 at 7:51:12 AM UTC+1, Jochen Eisinger wrote: > > This is a svn revision and has nothing to do with

Re: [v8-users] Runtime crash on trying to create a half-meg string

"git checkout -b 4.8 -t branch-heads/4.8" See https://github.com/v8/v8/wiki/Getting-Started-with-Embedding for more information. On Wednesday, February 10, 2016 at 12:02:55 PM UTC+1, Danny Dorfman wrote: > > Hello Jakob, > > Thank you for the quick response. Can you please help me fetch the

[v8-users] Re: Intent to remove hit count and ignore count for debug break points

ofrobots@, any clue about the node side? On Wednesday, January 20, 2016 at 8:50:29 AM UTC+1, Yang Guo wrote: > > Break points in the debugger currently track their hit count and have an > option for ignoring the next n hits. This feature is not used by Chrome > Devtools and will not be exposed

[v8-users] [PSA] Migration to new issue tracker happening next week

Hi, the V8 issue tracker (not Chromium) is going to migrate to Monorail next week on Tuesday evening CET. Please expect a few hours of down-time. Afterwards the new issue tracker should be ready for use. We will send out more details next week. If you have any questions, please do not

Re: [v8-users] Is there any up-to-date documentation on how to use v8::Debug

The whole debugging API is in flux and well, not maintained. Attaching a debugger is specific to the embedder so it is easier to do "spot consulting'. What are you planning to do? On Monday, November 9, 2015 at 11:58:14 PM UTC+1, Jane Chen wrote: > > Just went to this link: > >

Re: [v8-users] V8 Flags

You can also have a look at https://www.chromium.org/developers/how-tos/run-chromium-with-flags. Jakob is right, normally you don't want to mess with these if you are not actively working on V8/Chromium. Running d8 with '--help' will also show you the available flags with a short description.

[v8-users] Re: Setting project toolset when creating project files

1. GoTo https://code.google.com/p/v8-wiki/wiki/BuildingWithGYP 2. Search for Visual Studio 3. Do stuff mentioned there 4. Profit! :-) If setting the GYP variable didn't help please tell. On Monday, September 14, 2015 at 7:15:01 PM UTC+2, Nothing to See wrote: > > Hello, > > I

Re: [v8-users] whats the difference between v8::Handle and v8::Local ?

Unfortunately the transition is not complete yet. On Friday, September 4, 2015 at 3:27:08 PM UTC+2, Shezan Baig wrote: > > On Tuesday, March 10, 2015 at 4:28:10 AM UTC-4, Sven Panne wrote: >> >> On Tue, Mar 10, 2015 at 8:58 AM, David Xanatos >> wrote: >> >>> [...] and what

[v8-users] Re: build issue for v8

What other Visual Studio version have you installed? Have you done: If you have Visual Studio 2013 and 2015 installed side-by-side and set the environment variable GYP_MSVS_VERSION to '2013'. In that case the right project files are going to be created. ? On Friday, August 21, 2015 at 5:32:17

Re: [v8-users] Re: building V8: Getting error running python build\gyp_v8

...@googlegroups.com javascript: [ mailto:...@googlegroups.com javascript:] *On Behalf Of *Michael Hablich *Sent:* Wednesday, August 5, 2015 12:22 AM *To:* v8-users v8-u...@googlegroups.com javascript: *Subject:* [v8-users] Re: building V8: Getting error running python build\gyp_v8 I am confused

[v8-users] Re: building V8: Getting error running python build\gyp_v8

I am confused: python build\gyp_v8 generates the project files. Do you get an error while running this command or actually building the solution? Which VS version are you using (simultaneously)? There we recent threads on this group about building on Windows. Have you already checked them?

[v8-users] Re: Unable to build V8 library for Android in Mac - please advise

Hi Heriberto, few answers inline. On Tuesday, August 4, 2015 at 10:24:47 PM UTC+2, Heriberto Delgado wrote: Another update. First of all, let me tell you: I am a bit disappointed for the poor (actually, for the non-existent) support in this group for this issue. Is it really that

Re: [v8-users] Getting started tutorial problems

that the file is now called libv8_external_snapshot.a. The Getting-Started doc needs updating. On Mon, Aug 3, 2015 at 9:53 AM, Michael Hablich hab...@chromium.org wrote: Which V8 version are you trying to build? 4.3? On Monday, August 3, 2015 at 1:34:52 AM UTC+2, Jerrad Patch wrote: Nope

Re: [v8-users] Getting started tutorial problems

Which V8 version are you trying to build? 4.3? On Monday, August 3, 2015 at 1:34:52 AM UTC+2, Jerrad Patch wrote: Nope, that wasn't it. It seems that I am missing the archive file *snapshot.a. It wasn't built during the make x64.release. I tried removing the snapshot archive but got compile

Re: [v8-users] v8 crashing during garbage collector with a NULL-Pointer exception

Hi Wilfried, you can also have a look at https://code.google.com/p/v8-wiki/wiki/ReleaseProcess which describes the point of the different types of branches. Cheers, Michael On Wednesday, July 29, 2015 at 5:40:10 PM UTC+2, Jakob Kummerow wrote: On Wed, Jul 29, 2015 at 5:09 PM, Wilfried

[v8-users] V8's 4.5 release

Hi, V8 recently created a new major branch (4.5). This version is currently in beta. If you want to have an overview of the shipped features you should have a look at this http://v8project.blogspot.de/2015/07/v8-45-release.html blog post. Cheers, Michael -- -- v8-users mailing list

[v8-users] Re: How to run multiple files using v8

Hi, you can load a JavaScript file in D8 with the load(fileName) function e.g. load('test.js'); Be aware that V8 is a JavaScript engine but not an HTML renderer (that's Blink). This means that DOM elements (e.g. the window or document objects) are not supported in D8. Cheers, Michael On

[v8-users] Re: Segmentation Fault in hello-world program in v8

Hi have you tried building it with the latest stable release (4.3)? Our Getting Started https://developers.google.com/v8/get_started is only compatible with the latest stable release. On Monday, June 15, 2015 at 6:51:06 AM UTC+2, shubham goswami wrote: I have compiled v8 on Ubuntu and am now

[v8-users] Re: Need help with building v8 on win8.1 64 platform

Hi, - Is the system32 directory in your PATH? - Have you tried it after a restart? - Can you access https://src.chromium.org/svn/trunk/tools/third_party/python276_bin.zip manually? Please check this Chromium bug https://code.google.com/p/chromium/issues/detail?id=151645 for

Re: [v8-users] Why run Hello World error

Please be aware that the example on https://developers.google.com/v8/get_started#intro is compatible with the latest stable branch. Currently this is 4.2. If you want to check out this branch do the following steps in your Git repo: 1. git checkout -b 4.2 -t branch-heads/4.2 2. gclient

[v8-users] Re: Intent to implement: V8 extras

Hi Domenic, Jochen and Yang, this sounds really cool. Can you please add a link to an accessible design documentation? Collaboration will be much easier via GDocs. Thanks, Michael On Monday, May 11, 2015 at 7:52:25 PM UTC+2, Domenic Denicola wrote: Over the last two weeks we’ve been working

Re: [v8-users] Intent to Implement: SIMD.js

Hi Bill, thanks for re-posting your intend to implement to this group. Do you have an ETA on the design document, so I know when we can move forward with your feature? I have shared a new template for V8 design documents with you in order to make this step as smooth as possible. If you have

[v8-users] New handling of MIPS ports

Hi, *TL;DR; at the bottom* in the future MIPS will be a tree closer for V8. As a result the MIPS ports need to be handled more integrated with the general V8 development. I collaborated with Paul regarding this topic and we agreed on the following changes: *Straight-forward changes will be

[v8-users] API changes upcoming to make writing exception safe code more easy

. Cheers, Michael Hablich -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups v8-users group. To unsubscribe from this group and stop receiving emails from it, send an email