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

[Michael Hablich]

FYI, there were some small changes around the TAG review requirements:

"For smaller JavaScript or WebAssembly features, a TAG review is not
required, as TC39 and the Wasm CG already provide significant technical
oversight. If the feature is large or cross-cutting (e.g., requires changes
to 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 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
> <https://v8.dev/docs/feature-launch-process>.
>
> *Why this change? *
> The old V8 JS language launch process was created in a world before the
> revisited Blink intent process. Nowadays, besides JavaScript also
> WebAssembly is supported by V8. As a lot of WebAssembly-focused features
> are not only implemented in V8 but also in Chromium, V8's own Feature
> Launch Process was not adequate enough. Thus, for WebAssembly features the
> Blink-intent process is already used. In order to remove process complexity
> (and ambiguity) V8 is deprecating its own Feature Launch Process and fully
> adopt Blink-intent for JS features too.
>
> *Does this affect non-language features?*
> No, only features that change the Web Platform API need to follow Blink
> intents.
>
> If you have any questions, please feel free to get in touch with me.
>
> Cheers,
> Michael
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/CAF2MX8gzXUELc5gd7o4D7BUxy%3DZ9nRzb_NBmdauVrW2bGpqxxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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
.

*Why this change? *
The old V8 JS language launch process was created in a world before the
revisited Blink intent process. Nowadays, besides JavaScript also
WebAssembly is supported by V8. As a lot of WebAssembly-focused features
are not only implemented in V8 but also in Chromium, V8's own Feature
Launch Process was not adequate enough. Thus, for WebAssembly features the
Blink-intent process is already used. In order to remove process complexity
(and ambiguity) V8 is deprecating its own Feature Launch Process and fully
adopt Blink-intent for JS features too.

*Does this affect non-language features?*
No, only features that change the Web Platform API need to follow Blink
intents.

If you have any questions, please feel free to get in touch with me.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: Branch cut V8 7.5

[Michael Hablich]

Hi,

we have officially branched to be prepared for the upcoming Chrome version
75. It is based on one of the latest Chrome Canaries. We currently do *not*
roll back the version in Chromium, as the only delta is a MIPS CL, so it
does not have any effect on Chromium.

Integration into Chromium is stopped until Chromium has branched too.

V8 branch: branch-heads/7.5
Original Canary: 75.0.3769.0
Ref to be used in Chromium:
https://chromium.googlesource.com/v8/v8/+/refs/heads/7.5-lkgr

If your CL is not included in 75.0.3769.0 you might consider merging it
into the branch branch-heads/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 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
> point. This means we will roll this version into Chromium in order to give
> them and Blink time to synchronize with the roll. Essentially this will be
> a revert to an older version!
> In order to make this synchronization as painless as possible for V8 and
> Blink please don't make API changes which make the revert more difficult
> and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.
>
> THURSDAY 2019-04-18 Create 7.5 branch
> Create the branch based on one of the latest/most stable Canaries. The
> auto-roller is closed (maybe over the weekend). Keep in mind that this
> means we are not integrating with Chromium (much less test coverage). If
> you happen to work an an important fix, please make sure that the fix is on
> 7.5 too! See information on merging & patching for the details. Merge
> approvers for this release are Chrome Release Managers and hablich@.
>
> Latest MONDAY 2019-04-22: Back to normal and API adoption freeze is lifted
> Auto-roller is running again and we are back to normal business.
>
> Cheers,
> Michael
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.5

[Michael Hablich]

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
point. This means we will roll this version into Chromium in order to give
them and Blink time to synchronize with the roll. Essentially this will be
a revert to an older version!
In order to make this synchronization as painless as possible for V8 and
Blink please don't make API changes which make the revert more difficult
and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.

THURSDAY 2019-04-18 Create 7.5 branch
Create the branch based on one of the latest/most stable Canaries. The
auto-roller is closed (maybe over the weekend). Keep in mind that this
means we are not integrating with Chromium (much less test coverage). If
you happen to work an an important fix, please make sure that the fix is on
7.5 too! See information on merging & patching for the details. Merge
approvers for this release are Chrome Release Managers and hablich@.

Latest MONDAY 2019-04-22: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: Branch cut V8 7.4

[Michael Hablich]

Hi,

we have officially branched to be prepared for the upcoming Chrome version
74. 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.4
Original Canary: 74.0.3726.0

If your CL is not included in 74.0.3726.0 you might consider merging it
into the branch branch-heads/7.4. In that case please apply the label
Merge-Requested-7.4 to the bug the CL is fixing. See
hhttps://v8.dev/docs/merge-patch for more information on merging.

Thanks,
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 Beta phase for Chrome 74. On
> the 2019-03-07 one of the latest Canaries will be selected to be the
> branch point. This means we will roll this version into Chromium in order
> to give them and Blink time to synchronize with the roll. Essentially this
> will be a revert to an older version!
> In order to make this synchronization as painless as possible for V8 and
> Blink please don't make API changes which make the revert more difficult
> and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.
>
> THURSDAY 2019-03-07 Create 7.4 branch
> Create the branch based on one of the latest/most stable Canaries. The
> auto-roller is closed (maybe over the weekend). Keep in mind that this
> means we are not integrating with Chromium (much less test coverage). If
> you happen to work an an important fix, please make sure that the fix is on
> 7.4 too! See information on merging & patching for the details. Merge
> approvers for this release are Chrome Release Managers and hablich@.
>
> Latest MONDAY 2019-03-11: Back to normal and API adoption freeze is lifted
> Auto-roller is running again and we are back to normal business.
>
> Cheers,
> Michael
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.4

[Michael Hablich]

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 point.
This means we will roll this version into Chromium in order to give them
and Blink time to synchronize with the roll. Essentially this will be a
revert to an older version!
In order to make this synchronization as painless as possible for V8 and
Blink please don't make API changes which make the revert more difficult
and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.

THURSDAY 2019-03-07 Create 7.4 branch
Create the branch based on one of the latest/most stable Canaries. The
auto-roller is closed (maybe over the weekend). Keep in mind that this
means we are not integrating with Chromium (much less test coverage). If
you happen to work an an important fix, please make sure that the fix is on
7.4 too! See information on merging & patching for the details. Merge
approvers for this release are Chrome Release Managers and hablich@.

Latest MONDAY 2019-03-11: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 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 interested, please get in touch with
> me.
>
> It would also be good to know if your usage of V8 is reliant on the MIPS
> port.
>
> Cheers,
> Michael
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 interested, please get in touch with
me.

It would also be good to know if your usage of V8 is reliant on the MIPS
port.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.3

[Michael Hablich]

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
Original Canary: 73.0.3682.0
Ref to be used in Chromium:
https://chromium.googlesource.com/v8/v8/+/refs/heads/7.3-lkgr

If your CL is not included in 73.0.3682.0 you might consider merging it
into the branch branch-heads/7.3. In that case please apply the label
Merge-Requested-7.3 to the bug the CL is fixing. See
https://github.com/v8/v8/wiki/Merging%20&%20Patching for more information
on merging.

Thanks,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: Branch cut V8 7.2

[Michael Hablich]

Hi,

we have officially branched to be prepared for the upcoming Chrome version
72. Chromium master is already up to date.

Integration into Chromium is stopped until Chromium has branched too.

V8 branch: branch-heads/7.2
Original Canary: 72.0.3625.0
Ref to be used in Chromium:
https://chromium.googlesource.com/v8/v8/+/refs/heads/7.2-lkgr

If your CL is not included in 72.0.3625.0 you might consider merging it
into the branch branch-heads/7.2. In that case please apply the label
Merge-Requested-7.2 to the bug the CL is fixing. See
https://github.com/v8/v8/wiki/Merging%20&%20Patching 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
> 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
> point. This means we will roll this version into Chromium in order to give
> them and Blink time to synchronize with the roll. Essentially this will be
> a revert to an older version!
> In order to make this synchronization as painless as possible for V8 and
> Blink please don't make API changes which make the revert more difficult
> and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.
>
> THURSDAY 2018-11-29 Create 7.2 branch
> Create the branch based on one of the latest/most stable Canaries. The
> auto-roller is closed (maybe over the weekend). Keep in mind that this
> means we are not integrating with Chromium (much less test coverage). If
> you happen to work an an important fix, please make sure that the fix is on
> 7.2 too! See information on merging & patching for the details. Merge
> approvers for this release are Chrome Release Managers and hablich@.
>
> Latest MONDAY 2018-12-03: Back to normal and API adoption freeze is lifted
> Auto-roller is running again and we are back to normal business.
>
> Cheers,
> Michael
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.2

[Michael Hablich]

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
point. This means we will roll this version into Chromium in order to give
them and Blink time to synchronize with the roll. Essentially this will be
a revert to an older version!
In order to make this synchronization as painless as possible for V8 and
Blink please don't make API changes which make the revert more difficult
and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.

THURSDAY 2018-11-29 Create 7.2 branch
Create the branch based on one of the latest/most stable Canaries. The
auto-roller is closed (maybe over the weekend). Keep in mind that this
means we are not integrating with Chromium (much less test coverage). If
you happen to work an an important fix, please make sure that the fix is on
7.2 too! See information on merging & patching for the details. Merge
approvers for this release are Chrome Release Managers and hablich@.

Latest MONDAY 2018-12-03: Back to normal and API adoption freeze is lifted
Auto-roller is running again and we are back to normal business.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: Branch cut V8 7.1

[Michael Hablich]

Hi,

we have officially branched to be prepared for the upcoming Chrome version
71. 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.1
Original Canary: 71.0.3575.0
Ref to be used in Chromium:
https://chromium.googlesource.com/v8/v8/+/refs/heads/7.1-lkgr

If your CL is not included in 71.0.3575.0 you might consider merging it
into the branch branch-heads/7.0. In that case please apply the label
Merge-Requested-7.1 to the bug the CL 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.
>
> 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
> point. This means we will roll this version into Chromium in order to give
> them and Blink time to synchronize with the roll. Essentially this will be
> a revert to an older version!
> In order to make this synchronization as painless as possible for V8 and
> Blink please don't make API changes which make the revert more difficult
> and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.
>
> THURSDAY 2018-10-11 Create 7.1 branch
> Create the 710 based on one of the latest/most stable Canaries. The
> auto-roller is closed (maybe over the weekend). Keep in mind that this
> means we are not integrating with Chromium (much less test coverage). If
> you happen to work an an important fix, please make sure that the fix is on
> 7.1 too! See information on merging & patching for the details. Merge
> approvers for this release are Chrome Release Managers and hablich@.
>
> Cheers,
> Michael
>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.1

[Michael Hablich]

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
point. This means we will roll this version into Chromium in order to give
them and Blink time to synchronize with the roll. Essentially this will be
a revert to an older version!
In order to make this synchronization as painless as possible for V8 and
Blink please don't make API changes which make the revert more difficult
and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.

THURSDAY 2018-10-11 Create 7.1 branch
Create the 710 based on one of the latest/most stable Canaries. The
auto-roller is closed (maybe over the weekend). Keep in mind that this
means we are not integrating with Chromium (much less test coverage). If
you happen to work an an important fix, please make sure that the fix is on
7.1 too! See information on merging & patching for the details. Merge
approvers for this release are Chrome Release Managers and hablich@.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Arraybuffer

[Michael Hablich]

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* consulting 
blink-...@chromium.org and cs.chromium.org you still have questions about 
the *V8 codebase*, feel free to ask questions on v8-users@googlegroups.com.

Cheers,
Michael

On Friday, September 28, 2018 at 2:39:31 PM UTC+2, dan Med wrote:
>
> I appreciate your help, but still i can't seem to just understand the 
> stack calls and if i do that then i like to understand what thing should i 
> do in the code to get v8 execute those lines, well if my prievous question 
> is out of scope for v8-users how can i understand how they work ? 
> There is no doc
>
> Il giorno ven 28 set 2018 alle ore 14:35 Caitlin Potter  > ha scritto:
>
>> That question is probably out of scope for v8-users. The good news is, 
>> cs.chromium.org is very good at finding when things are called, how 
>> they’re used, etc.
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@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 to v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Branch cut V8 7.0

[Michael Hablich]

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
point. This means we will roll this version into Chromium in order to give
them and Blink time to synchronize with the roll. Essentially this will be
a revert to an older version!
In order to make this synchronization as painless as possible for V8 and
Blink please don't make API changes which make the revert more difficult
and don't adopt API changes. When in doubt, ask yangguo@ or hablich@.

THURSDAY 2018-08-30 Create 7.0 branch
Create the 7.0 based on one of the latest/most stable Canaries. The
auto-roller is closed (maybe over the weekend). Keep in mind that this
means we are not integrating with Chromium (much less test coverage). If
you happen to work an an important fix, please make sure that the fix is on
7.0 too! See information on merging & patching for the details. Merge
approvers for this release are Chrome Release Managers and hablich@.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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
'
doc. Plain git commands are already capable of creating such a list quite
easy e.g. 'git log branch-heads/6.2..branch-heads/6.3 include/v8.h' for the
6.3 release.

If you think that a curated API changes document offers sufficient value to
you, please ping this thread and provide your use case.

Thanks,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

Hmm, can you please create a bug report at
https://bugs.chromium.org/p/v8/issues/entry and include the following
information:

1.) Commit hash that you are trying to build
2.) Platform
3.) Exact steps you used until you reached "tools/dev/v8gen.py x64.release"

Cheers,
Michael

On Wed, Jul 26, 2017 at 12:37 PM Ross SimbioS <ross.sys...@gmail.com> wrote:

> Hi Michael.
> I went through all the steps on the instructions but error still here
>
> root@server:/opt/v8# tools/dev/v8gen.py x64.release
>
> Hint: You can raise verbosity (-vv) to see the output of failed commands.
>
> Traceback (most recent call last):
>   File "tools/dev/v8gen.py", line 304, in 
> sys.exit(gen.main())
>   File "tools/dev/v8gen.py", line 298, in main
> return self._options.func()
>   File "tools/dev/v8gen.py", line 166, in cmd_gen
> gn_outdir,
>   File "tools/dev/v8gen.py", line 208, in _call_cmd
> stderr=subprocess.STDOUT,
>   File "/usr/lib/python2.7/subprocess.py", line 574, in check_output
> raise CalledProcessError(retcode, cmd, output=output)
> subprocess.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
>
>
> On 26 July 2017 at 13:08, Michael Hablich <habl...@chromium.org> wrote:
>
>> 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 <ross.sys...@gmail.com>
>> wrote:
>>
>>> Hi.
>>> Please help me.
>>> My problem:
>>>
>>> root@server:/opt/v8/tools/dev# ./v8gen.py -vv x64.release
>>>
>>> 
>>> cd /opt/v8
>>>
>>> 
>>> /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
>>>   Traceback (most recent call last):
>>> File "tools/mb/mb.py", line 36, in 
>>>   import gn_helpers
>>>   ImportError: No module named gn_helpers
>>> Traceback (most recent call last):
>>>   File "./v8gen.py", line 304, in 
>>> sys.exit(gen.main())
>>>   File "./v8gen.py", line 298, in main
>>> return self._options.func()
>>>   File "./v8gen.py", line 166, in cmd_gen
>>> gn_outdir,
>>>   File "./v8gen.py", line 208, in _call_cmd
>>> stderr=subprocess.STDOUT,
>>>   File "/usr/lib/python2.7/subprocess.py", line 574, in check_output
>>> raise CalledProcessError(retcode, cmd, output=output)
>>> subprocess.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
>>>
>>> Python 2.7.12
>>>
>>> I can not understand what the problem is (
>>>
>>> Many thanks.
>>>
>>> --
>>> --
>>> 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 to v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> http://groups.google.com/group/v8-users
>> ---
>>
> You received this message because you are subscribed to a topic in the
>> Google Groups "v8-users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/v8-users/5qqum0FTWNE/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> v8-users+unsubscr...@googlegroups.com.
>>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Best Regards Ross
> Remote Server Administration.
> e-mail: ross.sys...@gmail.com
> skype:  ross.sysadm
> System Admin, Linux & Cloud Computing expert ready to complete your work
&

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

[Michael Hablich]

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
>
> 
> cd /opt/v8
>
> 
> /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
>   Traceback (most recent call last):
> File "tools/mb/mb.py", line 36, in 
>   import gn_helpers
>   ImportError: No module named gn_helpers
> Traceback (most recent call last):
>   File "./v8gen.py", line 304, in 
> sys.exit(gen.main())
>   File "./v8gen.py", line 298, in main
> return self._options.func()
>   File "./v8gen.py", line 166, in cmd_gen
> gn_outdir,
>   File "./v8gen.py", line 208, in _call_cmd
> stderr=subprocess.STDOUT,
>   File "/usr/lib/python2.7/subprocess.py", line 574, in check_output
> raise CalledProcessError(retcode, cmd, output=output)
> subprocess.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
>
> Python 2.7.12
>
> I can not understand what the problem is (
>
> Many thanks.
>
> --
> --
> 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 to v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 on a non-optimizing (FullCodeGen) and optimizing compiler
(Crankshaft) pair with the combination of an interpreter (Ignition) and a
new optimizing compiler (TurboFan).

You can try the new pipeline by setting an about:flags entry
 or
passing the flag "--future" to d8.
Eng contact emails

da...@chromium.org, bmeu...@chromium.org (TurboFan), rmcil...@chromium.org
(Ignition)
Design docs

TurboFan: https://github.com/v8/v8/wiki/TurboFan
Ignition: https://github.com/v8/v8/wiki/Interpreter
Planned date for the switch

March 2017.
Affected platforms

All
How to try the new architecture

This dedicated blog
 post
describes how the new pipeline can be switched on.
Debuggability

DevTools support is the same as with the classic pipeline.
Interoperability and Compatibility Risk

There are no user-facing changes (e.g. no new APIs changed). The new
pipeline will change V8's performance profile considerably. Real-world
JavaScript performance

should improve and V8 memory consumption should be reduced. We expect
controlled regressions in some synthetic JavaScript benchmarks like Octane.
We plan to purposefully address selected regressions in upcoming releases.

We are already A/B testing the new pipeline to Canary and Dev channel in
M58. Please note that individually, Ignition (on low memory devices and for
certain JavaScript features on all platforms) and TurboFan (for certain
JavaScript features) have been active for a long time (> half a year).
Additionally we have set-up dedicated tests for security, correctness,
performance and stability.
How to report bugs

As this is a major change in V8 we anticipate that unexpected, negative
side-effects in performance, memory profile, security or correctness might
occur. If you see anything, please feel encouraged to report a bug

.

If you have any concerns or remarks, please feel free to simply respond to
this thread or send a mail directly to habl...@chromium.org

Cheers,

Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 
Ignition+Turbofan.

As an embedder you already have the opportunity to try out the new 
configuration before it will be the default. You can use the specific 
instructions for Node.js 

 
or Chrome Canary 
 to 
get an idea on how to switch on the new architecture.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: ES2015 module support?

[Michael Hablich]

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 wrote:
>
> Are we any closer at this point? I'm seeing devs give up and revert to 
> prior chaos. Maybe a flag to enable something?
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

--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 limit.
>
> Since the code is the same, I want to try and rule out engine optimization 
> issues. Is there a V8 flag for disabling all of the optimizations?
>
>
> ☆*PhistucK*
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

IC. The optimization in TurboFan is likely going to stick. Keep in mind 
that this does not mean that try/catch magically gets faster though. Do you 
have performance comparisons for AMP for try/catch? That would be highly 
interesting.

Cheers,
Michael

On Monday, July 18, 2016 at 5:36:02 PM UTC+2, Ali Ghassemi wrote:
>
> Performance is fairly important in AMP (https://www.ampproject.org/) and 
> we try to optimize the JS code as much as possible. Currently we have 
> externed multiple try-catch statements out of busy functions and have a 
> small Closure compiler customization 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 is important to you?
>>
>> On Monday, July 18, 2016 at 3:14:29 PM UTC+2, Ali Ghassemi wrote:
>>>
>>> Hi V8 team,
>>>
>>> I am just wondering how I can find out when/if Try-Catch optimization 
>>> will ship with Turbofan/V8/Chrome. I know there has been a few attempts to 
>>> ship it and the latest is https://codereview.chromium.org/1996373002 
>>> but I can't tell ultimately what version of Chrome is planned to have that 
>>> change.
>>>
>>> Thanks,
>>> Ali
>>>
>>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 the issue tracker.
>
> Since we migrated from svn to git, there's sadly moi easy way to translate 
> svn links to git links, however, a quick search of the history leads to 
> https://chromium.googlesource.com/v8/v8/+/52c421956aac966a89f5d6158db50bad6b2c6d96
>
> On Thu, Mar 10, 2016, 6:26 AM Zaheer Ahmad  > wrote:
>
>> hi, May i know how i can access old issue list? e.g. 
>> https://bugs.chromium.org/p/v8/source/detail?r=17102 referred by 
>> https://chromiumcodereview.appspot.com/23477061 is not accessible.
>>
>> Thanks
>>
>> On Tue, Dec 8, 2015 at 1:02 PM,  
>> wrote:
>>
>>> This is now complete!
>>>
>>> You can see the new tracker here: https://bugs.chromium.org/p/v8
>>>
>>> Links to the old tracker automatically redirect: 
>>> https://code.google.com/p/v8/issues/detail?id=160
>>>
>>> If you run into any issues, please let us know at 
>>> https://bugs.chromium.org/p/monorail
>>>
>>> Thanks!
>>>
>>> -- 
>>> -- 
>>> v8-users mailing list
>>> v8-u...@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 to v8-users+u...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@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 to v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

"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 latest 
> *stable* release? (I can't seem to find the instructions in the V8 docs)
>
> D.
>
> On Wednesday, February 10, 2016 at 11:36:41 AM UTC+2, Jakob Kummerow wrote:
>>
>> Version "3.31" doesn't really exist. Yes we once created a branch of that 
>> name, but it was abandoned right after because it was in such a bad state 
>> that we gave up trying to stabilize it. It was never used in a Chrome 
>> stable channel release, which would have been your hint that it's ready for 
>> production.
>>
>> I'd guess that your string has nothing to do with the failure, it just so 
>> happens to be the allocation that triggers a GC round. Somehow spinning up 
>> the sweeper threads fails. If this were happening on the 4.8 or 4.9 branch, 
>> I'd investigate further... ;-)
>>
>> On Wed, Feb 10, 2016 at 9:59 AM, Danny Dorfman  
>> wrote:
>>
>>> Hello there,
>>>
>>> I am running with V8 3.31, the debug version, and I get this crash upon 
>>> allocating a large string:
>>>
>>> #0  0x7f0a6b0efb4b in v8::base::OS::Abort () at 
>>> ../src/base/platform/platform-posix.cc:210
>>> 210  if (g_hard_abort) {
>>> (gdb) bt
>>> #0  0x7f0a6b0efb4b in v8::base::OS::Abort () at 
>>> ../src/base/platform/platform-posix.cc:210
>>> #1  0x7f0a6b0ec208 in V8_Fatal (file=0x7f0a6b3c0c28 
>>> ".././src/base/platform/mutex.h", line=77, format=0x7f0a6b0f0e38 
>>> "CHECK_EQ(%s, %s) failed\n#   Expected: %i\n#   Found: %i") at 
>>> ../src/base/logging.cc:87
>>> #2  0x7f0a6aaa1b12 in CheckEqualsHelper (file=0x7f0a6b3c0c28 
>>> ".././src/base/platform/mutex.h", line=77, expected_source=0x7f0a6b3c0c26 
>>> "1", expected=1, value_source=0x7f0a6b3c0c1f "level_", value=2) at 
>>> .././src/base/logging.h:51
>>> #3  0x7f0a6b0ed084 in v8::base::Mutex::AssertHeldAndUnmark 
>>> (this=0x7f0ad84971a0) at .././src/base/platform/mutex.h:77
>>> #4  0x7f0a6b0ed934 in v8::base::Mutex::Unlock (this=0x7f0ad84971a0) 
>>> at ../src/base/platform/mutex.cc:134
>>> #5  0x7f0a6ad57df2 in 
>>> v8::internal::MarkCompactCollector::StartSweeperThreads 
>>> (this=0x7f0ad872ac68) at ../src/heap/mark-compact.cc:461
>>> #6  0x7f0a6ad625a2 in 
>>> v8::internal::MarkCompactCollector::SweepSpaces (this=0x7f0ad872ac68) at 
>>> ../src/heap/mark-compact.cc:4134
>>> #7  0x7f0a6ad573de in 
>>> v8::internal::MarkCompactCollector::CollectGarbage (this=0x7f0ad872ac68) at 
>>> ../src/heap/mark-compact.cc:313
>>> #8  0x7f0a6ad297ad in v8::internal::Heap::MarkCompact 
>>> (this=0x7f0ad8725d80) at ../src/heap/heap.cc:1205
>>> #9  0x7f0a6ad29182 in v8::internal::Heap::PerformGarbageCollection 
>>> (this=0x7f0ad8725d80, collector=v8::internal::MARK_COMPACTOR, 
>>> gc_callback_flags=v8::kNoGCCallbackFlags) at ../src/heap/heap.cc:1095
>>> #10 0x7f0a6ad2851c in v8::internal::Heap::CollectGarbage 
>>> (this=0x7f0ad8725d80, collector=v8::internal::MARK_COMPACTOR, 
>>> gc_reason=0x7f0a6b166db4 "last resort gc", collector_reason=0x0, 
>>> gc_callback_flags=v8::kNoGCCallbackFlags) at ./src/heap/heap.cc:843
>>> #11 0x7f0a6ad2819c in v8::internal::Heap::CollectAllAvailableGarbage 
>>> (this=0x7f0ad8725d80, gc_reason=0x7f0a6b166db4 "last resort gc") at 
>>> ../src/heap/heap.cc:762
>>> #12 0x7f0a6acc31ed in v8::internal::Factory::NewRawTwoByteString 
>>> (this=0x7f0ad8725d60, length=431158, pretenure=v8::internal::NOT_TENURED) 
>>> at ../src/factory.cc:385
>>> #13 0x7f0a6acc0ff0 in v8::internal::Factory::NewStringFromUtf8 
>>> (this=0x7f0ad8725d60, string=..., pretenure=v8::internal::NOT_TENURED) at 
>>> ../src/factory.cc:247
>>> #14 0x7f0a6aada0fa in v8::(anonymous namespace)::NewString 
>>> (factory=0x7f0ad8725d60, type=v8::String::kNormalString, string=...) at 
>>> ../src/api.cc:5452
>>> #15 0x7f0a6aaeaad6 in v8::(anonymous namespace)::NewString 
>>> (v8_isolate=0x7f0ad8725d60, location=0x7f0a6b0f8ed4 
>>> "v8::String::NewFromUtf8()", env=0x7f0a6b0f8ec0 "String::NewFromUtf8", 
>>>  data=0x7f0ad853f660 '/' , "\n// x \n// ", '-' 
>>> , "\n\n//"..., type=v8::String::kNormalString, 
>>> length=431185)  at ../src/api.cc:5496
>>> #16 0x7f0a6aada20b in v8::String::NewFromUtf8 
>>> (isolate=0x7f0ad8725d60, data=0x7f0ad853f660 '/' , 
>>> "\n// x \n// ", '-' , "\n\n//"..., 
>>> type=v8::String::kNormalString, length=431185) at ../src/api.cc:5515
>>> - - - - - - 
>>>
>>> My code appears in the next frame, and says something like:
>>> v8::Local vSource = v8::String::NewFromUtf8(isolate, src, 
>>> v8::String::kNormalString, len);
>>>
>>> As you can see, the string is quite large (431185 bytes long). Any idea 
>>> why this is happening? What can I do about this?
>>>
>>> Regards,
>>> Danny
>>>
>>>
>>> -- 
>>> -- 
>>> 

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

[Michael Hablich]

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 once V8 eventually switches to Devtools 
> protocol as debugging API. I have a CL to remove this: 
> https://codereview.chromium.org/1607943003/
>
> Please speak up if you rely on this feature.
>
> Regards,
>
> Yang
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 hesitate to contact me or ask 
directly in this thread.

Thanks,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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:
>
> https://chromium.googlesource.com/v8/v8/+/master/docs/debugger_protocol.md
>
> and found that "*The message based API is no longer maintained.*"
>
> Does that mean that users (or embedders) should no longer use the message 
> based API since it is no longer supported?
>
> On Thursday, October 30, 2014 at 5:29:13 AM UTC-7, Ben Noordhuis wrote:
>>
>> On Thu, Oct 30, 2014 at 12:08 AM, Mark Tarrabain  
>> wrote: 
>> > Somebody, please help! 
>> > 
>> > lineprocessor.cc, which is referred to by the wiki at 
>> > https://code.google.com/p/v8/wiki/AddDebuggerSupport, doesn't seem to 
>> > contain any references at all to the v8::Debug class.   The wiki itself 
>> > refers to using the function v8::Debug::EnableAgent, but this function 
>> does 
>> > not seem to exist in the declaration of v8::Debug.   I'm finding myself 
>> so 
>> > completely lost that I don't even have the words for it. 
>> > 
>> > Can anyone please point me in the direction of either an explanation 
>> that is 
>> > reflective of how the code actually exists today, or else examples of 
>> how to 
>> > use the debugger facilities in v8? 
>>
>> The basic mode of operation is where you feed the debugger commands 
>> with v8::Debug::SendCommand().  The protocol is described here: 
>> https://code.google.com/p/v8/wiki/DebuggerProtocol 
>>
>> v8::Debug::SendCommand() is thread-safe (you can call it from a 
>> different thread than the one executing JS) but not async signal-safe 
>> (you can't call it from a signal handler.) 
>>
>> You can interrupt a running script by calling v8::Debug::DebugBreak() 
>> from another thread.  It's de facto async signal-safe if, perhaps, not 
>> de jure; that is, I don't know whether V8 guarantees that it's async 
>> signal-safe but the current implementation is. 
>>
>> You can do more advanced things programmatically with 
>> v8::Debug::SetDebugEventListener() and v8::Debug::SetMessageHandler(). 
>> See test/cctest/test-debug.cc for more details. 
>>
>> V8 used to have an embedded debug agent that created a TCP listen 
>> socket for clients to connect to.  That was removed recently, you have 
>> to implement your own now. 
>>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] V8 Flags

[Michael Hablich]

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.

On Thursday, October 29, 2015 at 10:22:01 AM UTC+1, Jakob Kummerow wrote:
>
> https://chromium.googlesource.com/v8/v8/+/master/src/flag-definitions.h
>
> Spoiler: there's nothing in there that you'd want to mess with. Most flags 
> are for debugging and development. When it makes sense to turn on a flag, 
> we turn it on by default.
>
> On Thu, Oct 29, 2015 at 9:39 AM, Ivan P.  > wrote:
>
>> I know that Chrome V8 Engine has some option that can be set like 
>> "command-line" flags using v8::V8::SetFlagsFromString(). But where can I 
>> find description of the each flag? I did not succeed with googling for this 
>> info so far. Does anyone know the place in documentation or some other 
>> resource that describes V8 flags?
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@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 to v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

   
   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 have both Visual Studio 2015 and 2013 installed. When I use GYP to 
> create the V8 project files, it automatically sets the toolset version to 
> v140 (which is used in Visual Studio 2015). The project I need to use V8 in 
> uses the v120 toolset (which is Visual Studio 2013). Therefore, I always 
> have to change the toolset for every project file each time I update V8 
> back to v120. Is there any way to tell GYP it should use v120 
> unconditionally?
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 about v8::Persistent is that repalced by v8::Global?
>>>
>>
>> If you're working with a bleeding edge v8, you should use v8::Global 
>> already.
>>
>
>
> The V8 embedder's guide [1] still mentioned using v8::UniquePersistent or 
> v8::Persistent.  Should that be updated to suggest using v8::Global instead?
>
> [1] https://developers.google.com/v8/embed#handles-and-garbage-collection
>

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] Re: build issue for v8

[Michael Hablich]

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 AM UTC+2, Akshay Galande wrote:

 Hi,
 I was trying to checkout v8 code and build it for the first time.
 I followed the instructions on page: 
 https://code.google.com/p/v8-wiki/wiki/BuildingWithGYP

 Finally when I generated project files by executing the command python 
 build\gyp_v8 -Dtarget_arch=x64 and then tried to open All.sln file in the 
 visual studio it shows an error message several of .vcproj files in the 
 solution are not compatible with visual studio. It also says that visual 
 studio will do one time upgrade to these file.
 After I click OK, visual studio opens but solution explorer shows that all 
 modules are not compatible.

 Is my All.sln project file not building properly?
 I am using Visual Studio Express 2013.

 Thanks,


 -- 
 Just do it!!!


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

Looks ok. Unfortunately I don't have a Windows machine to check it out 
myself. Try running 'fetch v8 ' as mentioned 
in https://code.google.com/p/v8-wiki/wiki/UsingGit.

On Wednesday, August 5, 2015 at 6:57:51 PM UTC+2, gamert...@gmail.com wrote:

 I decided to start over and try again, doing my best to carefully follow 
 the instructions.

  

 When I install depot_tools following this site: 
 http://dev.chromium.org/developers/how-tos/install-depot-tools

 I followed the non-cygwin path.

  

 When I try this:

 *Non-cygwin:** Run **gclient** from the **cmd** shell**. The first time 
 it is run, it will install its own copy of svn and other tools. If you run 
 gclient from a non-cmd shell, it may appear to run properly, but svn, 
 python, and other tools may not get installed correctly (while it should 
 work fine from a msys bash shell, you may still trip over bugs from time to 
 time).*

 I see it install python 2.7.6, git 1.9.5, and then the gclient.py usage 
 info:

 Installing python 2.7.6...

 Fetching from 
 https://src.chromium.org/svn/trunk/tools/third_party/python276_bin.zip

 Installing git 1.9.5.chromium.6 (avg 1-2 min download) ...

 Fetching from 
 https://commondatastorage.googleapis.com/chrome-infra/git-1.9.5.chromium.6_bin.zip

 Usage: gclient.py command [options]

  

 Meta checkout manager supporting both Subversion and GIT.

  

 Commands are:

   cleanup  cleans up all working copies

   config   creates a .gclient file in the current directory

 snip

  

 Is this expected? I remember this happened the first time as well. 

  

  

 *From:* gamert...@gmail.com javascript: [mailto:gamert...@gmail.com 
 javascript:] 
 *Sent:* Wednesday, August 5, 2015 8:29 AM
 *To:* v8-u...@googlegroups.com javascript:
 *Subject:* RE: [v8-users] Re: building V8: Getting error running python 
 build\gyp_v8

  

 Hi,

 I’m using Visual Studio 2013.  I was able to successfully run 
 build\gyp_v8, but I get the below errors when building the solution.

  

 e.g. 

 Error  3  error C1083: Cannot open source file: 
 '..\..\build\Debug\obj\global_intermediate\experimental-libraries.cc': No 
 such file or directory   D:\projects\v8\v8\tools\gyp\c1xx   
 v8_nosnapshot

  

 Failed when I tried this on the machine when it was Win8.1, and also when 
 I just upgraded it to Win10 (doubt that this matters).

  

 *From:* v8-u...@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: 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?

  

  


 On Wednesday, August 5, 2015 at 6:52:28 AM UTC+2, gamert...@gmail.com 
 wrote:

 Hi,

  

 I'm following the directions here:

 https://code.google.com/p/v8-wiki/wiki/BuildingWithGYP

  

 I'm running on a Windows 8 machine, trying to build V8 with Visual 
 Studio.  

  

 I was able to successfully generate the project files, but when I do a 
 build, I get errors like:

  

 15c1xx : fatal error C1083: Cannot open source file:

 '..\..\build\Debug\obj\global_intermediate\code-stub-libraries.cc': No 
 such file or directory

  

 Unsurprisingly, those .cc files don't exist in that folder.  

  

 Does anyone know what can be going on?

  

 Thanks!

 -- 
 -- 
 v8-users mailing list
 v8-u...@googlegroups.com javascript:
 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 to v8-users+u...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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?



On Wednesday, August 5, 2015 at 6:52:28 AM UTC+2, gamert...@gmail.com wrote:

 Hi,

  

 I'm following the directions here:

 https://code.google.com/p/v8-wiki/wiki/BuildingWithGYP

  

 I'm running on a Windows 8 machine, trying to build V8 with Visual 
 Studio.  

  

 I was able to successfully generate the project files, but when I do a 
 build, I get errors like:

  

 15c1xx : fatal error C1083: Cannot open source file:

 '..\..\build\Debug\obj\global_intermediate\code-stub-libraries.cc': No 
 such file or directory

  

 Unsurprisingly, those .cc files don't exist in that folder.  

  

 Does anyone know what can be going on?

  

 Thanks!


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 atypical that someone attempts to build an Android version 
 of V8 using a recent Mac model with the latest tools available? 


It seems so, else you would have gotten any response. There are similar 
threads for other OS were people got feedback because other developers have 
the same/similar build configuration.
 

 Makes you wonder if Google is really *that* commited to open-source 
 software development, in spirit - as opposed to in letter, as Google 
 clearly is...

 Oh well.

 I finally got version 4.3.60 to compile and produce valid (full, instead 
 of thin) libraries for arm-eabi, arm64, x86, x64 and mips (but no mips64). 
 A modification was needed in \tools\gyp\v8.gyp to do that. Attached is the 
 modified v8.gyp with the modifications.

 I chose 4.3.60 since it was the last version I could compile by using the 
 steps below. Any versions after this one use the new compilation method 
 (that is, the one where you do not need to specify an ANDROID_NDK_ROOT 
 environment variable) and, it seems, are no longer able to produce fat v8 
 libraries.

 A few points of interest if you want to do the same:

 - This applies for version 4.3.60 only - check your local git copy for a 
 4.3.60 tag.
 - You will need *both* Xcode and the Command Line Development tools 
 installed in your machine.
 - Overwrite the current /tools/gyp/v8.gyp file with the attached one, in 
 order to produce fat (instead of thin) libraries.
 - This version uses the old compilation method, so be sure to  export 
 ANDROID_NDK_ROOT=~/Path/To/Your/Android/NDK/Folder/ .
 - If you attempt to include internationalization support, the system will 
 generate a few ICU library files, but they are all thin and cannot be 
 used in your project. I still haven't found a way to make them fat.
 - By all means, do include -j16 in your build command (or a similar 
 number); it will speed up the compilation considerably.


Yes, be aware that this depends on the cores you are having on your machine.
 

 - VERY IMPORTANT: The debugging agent that was present in version 3.14 is 
 *gone* now, for good. See 
 https://groups.google.com/forum/#!msg/v8-users/pS5tgGXzzHY/qG2txmrfqcAJ . 
 The debugging protocol and related functions, however, are still there; the 
 only thing you need to implement externally is the thread code that creates 
 a socket that sends and receive debugging commands outside the app.


 Now, to create the Android builds on a (recent model) Mac:

 - Install depot_tools ( 
 http://dev.chromium.org/developers/how-tos/install-depot-tools )
 - Open Terminal, then run the following commands:
fetch v8
cd v8
 - Using your favorite git client, checkout 4.3.60 in the v8 folder.
 - In Terminal, run:
   gclient sync
 - Copy the attached file to the /tools/gyp folder, overwriting the 
 existing one.
 - In Terminal, run:
export ANDROID_NDK_ROOT=/The/Full/Path/To/Your/Android/NDK/Folder/

 With this, you're ready to build the make commands for the various v8 
 libraries. In Terminal, run:

make android_arm.release -j16 i18nsupport=off
make android_arm64.release -j16 i18nsupport=off
make android_ia32.release -j16 i18nsupport=off
make android_x64.release -j16 i18nsupport=off
make android_mipsel.release -j16 i18nsupport=off

 The new library files are stored in folders called:

/out/android_arm.release
/out/android_arm64.release
/out/android_ia32.release
/out/android_x64.release
/out/android_mipsel.release
  
 Containing these files at each one of these folders:

   libv8_base.a
   libv8_libbase.a
   libv8_libplatform.a
   libv8_nosnapshot.a
   libv8_snapshot.a

 These are the files you want; just remember to choose one of 
 libv8_snapshot.a or libv8_nosnapshot.a depending on your project's needs.

 Hope this helps for anyone else that might have these issues.



 El viernes, 17 de julio de 2015, 9:14:55 (UTC-6), Heriberto Delgado 
 escribió:

 Environment:

 - MacBook Pro (Retina, 15-inch, Mid 2014)
 - OSX Yosemite (10.10.4)
 - Xcode 6.4
 - Android Studio 1.3 RC 1 (141.2071668)

 My intent is to compile V8 as a shared library so I can include it in my 
 new project as a standalone Javascript engine.

 These are the steps I followed starting July 16, 2015 in order to 
 accomplish that task:

 1) Used SourceTree to clone depot_tools into ~/Projects/depot_tools

 2) Started Terminal, then:

 export PATH=~/Projects/depot_tools:$PATH

 cd Projects

 fetch v8(took about 15 min.)

 3) As suggested in https://code.google.com/p/v8-wiki/wiki/D8OnAndroid , 
 opened ~/Projects/.gclient and added:

 target_os = [‘android’]

 And then, on Terminal:
 
 cd v8

 gclient sync —nohooks  

Re: [v8-users] Getting started tutorial problems

[Michael Hablich]

Answers inline

On Tuesday, August 4, 2015 at 4:59:48 AM UTC+2, Jerrad Patch wrote:

 this version is the latest version, not sure how to check that with the 
 depot_tools program. I tried the help with fetch --help but it doesnt show 
 --version.


Getting Started is only compatible with the current Stable version. I am 
currently updating it to be compatible with version 4.4.

Try 'git checkout -b 4.3 -t branch-heads/4.3' and afterwards 'gclient sync' 
to get a version directly.
 

 I have updated the archive to use *externap_snapshot.a, but I still get 
 compile errors. I am using the x64.release, and the sample code from the 
 getting started website. Does anyone have some working sample code I can 
 compile with the latest version that fetch v8 downloads. Thanks again for 
 all the replies.


On 'master' (and 'branch-heads/4.5') there is a directory called samples. 
The the compatible sample code can be found there (starting with version 
4.5).
 


 error I am getting

 jerrad@ubuntu:/host/v8/v8$ g++ -I. hello_world.cpp -o hello_world 
 -Wl,--start-group 
 out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,external_snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a
  
 -Wl,--end-group -lrt -pthread -std=c++0x

 hello_world.cpp: In function ‘int main(int, char**)’:
 hello_world.cpp:14:35: error: no matching function for call to 
 ‘v8::Isolate::New()’
Isolate* isolate = Isolate::New();
^
 hello_world.cpp:14:35: note: candidate is:
 In file included from hello_world.cpp:1:0:
 include/v8.h:5357:19: note: static v8::Isolate* v8::Isolate::New(const 
 v8::Isolate::CreateParams)
static Isolate* New(const CreateParams params);
^
 include/v8.h:5357:19: note:   candidate expects 1 argument, 0 provided



Please try the following steps:

   1. Goto v8/
   2. git checkout -b 4.5 -t branch-heads/4.5
   3. Copy samples/hello-world.cc to v8/
   4. git checkout -b 4.4 -t branch-heads/4.4
   5. gclient sync
   6. make x64.release snapshot=off
   7. g++ -I. hello-world.cc -o hello_world -Wl,--start-group 
   
out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,nosnapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a
 
   -Wl,--end-group -lrt -ldl -pthread -std=c++0x
   8. ./hello_world

 

 On Monday, August 3, 2015 at 4:02:30 AM UTC-4, Jakob Kummerow wrote:

 It appears 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, 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 errors for 
 hello_world.cpp

 the following 
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,
 snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a 
  -Wl,--end-group -lrt -pthread -std=c++0x 

 became
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase
 ,libplatform},third_party/icu/libicu{uc,i18n,data}}.a 
  -Wl,--end-group -lrt -pthread -std=c++0x 

 I will try to use the a32.release and see if it builds correctly. Any 
 ideas why *snapshot.a wouldnt exist after a build?


 On Sunday, August 2, 2015 at 6:25:14 PM UTC-4, Ben Noordhuis wrote:

 On Sun, Aug 2, 2015 at 11:48 PM, Jerrad Patch jerra...@gmail.com 
 wrote: 
  Hey, Ben. Thanks for the reply. I have fixed that error 
  
  here is the command: 
  
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  
 out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a
  

  -Wl,--end-group -lrt -pthread -std=c++0x 
  
  here is the error:g++: error: 
  out/x64.release/obj.target/tools/gyp/libv8_snapshot.a: No such file 
 or 
  directory 
  
  and if I go to the /V8/v8/out/x64.release/obj.target/tools/gyp 
 directory the 
  file does not exist, 
  
  I did not receive any compilation errors when building V8, so I am 
 wondering 
  if I should be using a different lib file in the */gyp folder? 

 Quite possibly.  `find out/ -name \*.a` should find all the archive 
 files, just update the paths accordingly. 

 -- 
 -- 
 v8-users mailing list
 v8-u...@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 to v8-users+u...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http

Re: [v8-users] Getting started tutorial problems

[Michael Hablich]

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 errors for 
 hello_world.cpp

 the following 
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,
 snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a 
  -Wl,--end-group -lrt -pthread -std=c++0x 

 became
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase
 ,libplatform},third_party/icu/libicu{uc,i18n,data}}.a 
  -Wl,--end-group -lrt -pthread -std=c++0x 

 I will try to use the a32.release and see if it builds correctly. Any 
 ideas why *snapshot.a wouldnt exist after a build?


 On Sunday, August 2, 2015 at 6:25:14 PM UTC-4, Ben Noordhuis wrote:

 On Sun, Aug 2, 2015 at 11:48 PM, Jerrad Patch jerra...@gmail.com 
 wrote: 
  Hey, Ben. Thanks for the reply. I have fixed that error 
  
  here is the command: 
  
  jerrad@ubuntu:/V8/v8$ g++ -I. hello_world.cpp -o hello_world 
  -Wl,--start-group 
  
 out/x64.release/obj.target/{tools/gyp/libv8_{base,libbase,snapshot,libplatform},third_party/icu/libicu{uc,i18n,data}}.a
  

  -Wl,--end-group -lrt -pthread -std=c++0x 
  
  here is the error:g++: error: 
  out/x64.release/obj.target/tools/gyp/libv8_snapshot.a: No such file or 
  directory 
  
  and if I go to the /V8/v8/out/x64.release/obj.target/tools/gyp 
 directory the 
  file does not exist, 
  
  I did not receive any compilation errors when building V8, so I am 
 wondering 
  if I should be using a different lib file in the */gyp folder? 

 Quite possibly.  `find out/ -name \*.a` should find all the archive 
 files, just update the paths accordingly. 



-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 Gösgens doth...@gmail.com 
 javascript: wrote:

 Ok, 
 looking at...
 https://gist.github.com/domenic/aca7774a5d94156bfcc1
 would give me this URL:
 https://chromium.googlesource.com/v8/v8.git/+/branch-heads/4.1 


 How does it give you 4.1? It tells you to use the same branch as stable 
 Chrome, no? Which is 4.4, as I've said before.
  

 which reads:

 Version 4.1.0.27 (cherry-pick)

 Correct, that's the tip of the 4.1 branch.

 But git only shows me versions with 3.xx and 4.2.xx, 4.3.xx, 4.5.xx and 
 4.6.xx?


 Huh?
 $ git log -1 --pretty=oneline branch-heads/4.1
 901b67916dc2626158f42af5b5c520ede8752da2 Version 4.1.0.27 (cherry-pick)

 Whats the point in having a 3 pages long Readme

 Huh? What 3-pages long Readme? 

 *Look at the V8 version x.y.z.w of Chrome-Stable on omahaproxy.com 
 http://omahaproxy.com (second-to-last column), take the x.y part and 
 plug it into chromium.googlesource.com/v8/v8.git/+/branch-heads/x.y 
 http://chromium.googlesource.com/v8/v8.git/+/branch-heads/x.y. *

 Done, that's it. If even that is too long for your taste, use this 
 approximation:

 *Look at the V8 version x.y.z.w of Chrome-Stable on omahaproxy.com 
 http://omahaproxy.com.*

  how to find out which is a release instead of having a wiki page with 
 '1.5.2015 V8 release xyz, maintained until 15.6.2015'? 

 Because that wiki page would both be more verbose than the one-liner 
 above, and quite boring to update every six weeks. 

 Being a long time Contributor to citadel.org and libical, we also got 
 down to doing something like this - Even with a changelog listing the 
 features.

 Reading the GIST, I guess (once more..) the last stable release before 
 3.31.74.1 was 3.29.88.19 ?


 Nope, there was a branch-heads/3.30 in between those two. But don't use 
 that, it's outdated, it has known security/stability bugs which will never 
 be patched. (You seem to think that 3.x is somehow better than 4.x. It's 
 not. Not more stable either. Just more outdated.)
  


 On Wednesday, July 29, 2015 at 3:54:26 PM UTC+2, Jakob Kummerow wrote:

 On Wed, Jul 29, 2015 at 2:50 PM, Wilfried Gösgens doth...@gmail.com 
 wrote:

 Hm, that explains a lot.
 Its pretty hard to tell what actually _is_ a v8 release and what not. 


 In an open source world, every commit is a release. We happen to 
 create 1-3 daily snapshots that have version numbers, mostly to make it 
 easier to talk about them.
  

 The closest thing I could find was browse 
 http://omahaproxy.appspot.com/ - 


 Could have searched this list, would have found e.g. 
 https://groups.google.com/forum/#!topic/v8-users/RkobpinkoKM with 
 detailed instructions and examples.
  

 and whenever all 'stable' columns point to the same version, thats a 
 release.


 Picking whatever is shipping in Chrome-stable is a reasonable rule of 
 thumb. (Stable versions for Linux/Mac/Windows should always be in sync; 
 CrOS and Android often lag behind a few days.)
  

 Is there a better way? and which was the next stable release after 
 3.31.74.1?


 The stable branch you're asking for is branch-heads/4.1, but note that 
 this, too, has reached its end of life months ago. The currently supported 
 stable branch is branch-heads/4.4. Every branch has a support period of 6 
 weeks, there are no long-term support branches or anything like that.
  


 On Wednesday, July 29, 2015 at 2:24:31 PM UTC+2, Jakob Kummerow wrote:

 3.31.74.1 was a failed attempt at creating a sufficiently stable basis 
 for a branch point, and is totally unsupported. Pretty bad idea to use 
 that 
 in production. I'm not surprised it's crashing.


 --- 
 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 to v8-users+u...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.






-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] V8's 4.5 release

[Michael Hablich]

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@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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 Wednesday, June 17, 2015 at 7:24:44 AM UTC+2, shubham goswami wrote:

 Hi

 I have an index.html file which calls a javascript file. This javascript 
 file in turn calls some other javascript files. How do I run multiple 
 javascript files using v8 engine?
 Also, are there any tutorials available on internet which can help in 
 writing code to run javascript using v8?

 Thanks


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 trying to get the sample 
 hello-world.cpp working, however, when I execute it I get a Segmentation 
 fault. Here is my source code:
 #include include/v8.h
 #include include/libplatform/libplatform.h

 using namespace v8;

 int main(int argc, char* argv[]) {
   // Initialize V8.
   V8::InitializeICU();
   //V8::Initialize();
   Platform* platform = platform::CreateDefaultPlatform();
   V8::InitializePlatform(platform);
   V8::Initialize();

   // Create a new Isolate and make it the current one.
   Isolate* isolate = Isolate::New();
   {

 Isolate::Scope isolate_scope(isolate);

 // Create a stack-allocated handle scope.
 HandleScope handle_scope(isolate);

 // Create a new context.
 LocalContext context = Context::New(isolate);

 // Enter the context for compiling and running the hello world script.
 Context::Scope context_scope(context);

 // Create a string containing the JavaScript source code.
 LocalString source = String::NewFromUtf8(isolate, 'Hello' + ', 
 World!');

 // Compile the source code.
 LocalScript script = Script::Compile(source);

 // Run the script to get the result.
 LocalValue result = script-Run();

 // Convert the result to an UTF8 string and print it.
 String::Utf8Value utf8(result);
 printf(%s\n, *utf8);
   }
   
   // Dispose the isolate and tear down V8.
   isolate-Dispose();
   V8::Dispose();
   V8::ShutdownPlatform();
   delete platform;
   return 0;
 }
 To compile, I use the following command:
 g++ -I. hello_world.cpp -o hello_world -Wl,--start-group out/native/obj.
 target/{tools/gyp/libv8_{base,libbase,snapshot,libplatform},third_party/
 icu/libicu{uc,i18n,data}}.a -Wl,--end-group -lrt -ldl -pthread -std=c++0x


 To run, I use
 ./hello_world

 I have just started using v8 and I am unable to figure out the error.
 However, when I run this piece of code, it runs fjust fine.

 #include include/v8.h
 #include include/libplatform/libplatform.h

 using namespace v8;

 int main(int argc, char* argv[]) {
   // Get the default Isolate created at startup.
   V8::Initialize();
   Isolate* isolate = Isolate::GetCurrent();
   if(!isolate) {
 isolate = v8::Isolate::New();
 isolate-Enter();
   }
   // Create a stack-allocated handle scope.
   HandleScope handle_scope(isolate);

   return 0;
 }

 Any help would be appreciated. Thanks!




-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 additional 
info.

Cheers,
Michael

On Wednesday, June 3, 2015 at 9:31:50 PM UTC+2, Tusshki Jain wrote:

 Hi Folks,

 I am trying to follow the instructions as much I can, I have installed 
 depot_tools already. 
 When I type gclient at my console it gives the following message:
 Installing python 2.7.6...
 Fetching from 
 https://src.chromium.org/svn/trunk/tools/third_party/python276_bin.zip
 'cscript' is not recognized as an internal or external command,
 operable program or batch file.
 ... Failed to checkout python automatically.
 You should get the prebaked version at 
 https://src.chromium.org/svn/trunk/tools/third_party/

 Though I have already placed python 2.7.6 executable in the system path + 
 i have place all the prebaked files of python in the depot_tools directory 
 itself.

 If any one have any idea with this issue. please let me know.

 Regards,
 TJ


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 sync
   3. Rebuild V8
   4. Rebuild example

Cheers,
Michael

On Tuesday, May 19, 2015 at 12:14:34 PM UTC+2, Ben Noordhuis wrote:

 On Tue, May 19, 2015 at 11:59 AM, miser udm...@gmail.com javascript: 
 wrote: 
  I just started learning v8, I download and build on OS X Yosemite‎, but 
 run 
  hello_world.cpp get some errors. 
  
  terminal： 
  
  g++ -Iinclude hello_world.cpp -o hello_world -Wl,--start-group 
  out/native/libv8_base.a  out/native/libv8_libbase.a 
  out/native/libv8_snapshot.a out/native/libv8_libplatform.a 
  out/native/libicuuc.a out/native/libicui18n.a out/native/libicudata.a 
  -Wl,--end-group -lrt -pthread 
  
  out: 
  In file included from hello_world.cpp:1: 
  include/v8.h:336:16: warning: alias declarations are a C++11 extension 
[-Wc++11-extensions] 
  using Handle = LocalT; 
 ^ 
  include/v8.h:352:33: error: use of undeclared identifier 'nullptr' 
V8_INLINE MaybeLocal() : val_(nullptr) {} 
  ^ 
  include/v8.h:359:51: error: use of undeclared identifier 'nullptr' 
V8_INLINE bool IsEmpty() const { return val_ == nullptr; } 
^ 
  include/v8.h:363:29: error: use of undeclared identifier 'nullptr' 
  out-val_ = IsEmpty() ? nullptr : this-val_; 
  ^ 
  include/v8.h:429:50: error: use of undeclared identifier 'nullptr' 
bool IsFirstPass() const { return callback_ != nullptr; } 
   ^ 
  include/v8.h:468:29: warning: alias declarations are a C++11 extension 
[-Wc++11-extensions] 
  using PhantomCallbackData = WeakCallbackInfoT; 
  ^ 
  include/v8.h:471:6: warning: scoped enumerations are a C++11 extension 
[-Wc++11-extensions] 
  enum class WeakCallbackType { kParameter, kInternalFields }; 
   ^ 
  include/v8.h:634:43: warning: deleted function definitions are a C++11 
  extension 
[-Wc++11-extensions] 
PersistentBase(PersistentBase other) = delete;  // NOLINT 
^ 
  include/v8.h:635:37: warning: deleted function definitions are a C++11 
  extension 
[-Wc++11-extensions] 
void operator=(PersistentBase) = delete; 
  ^ 
  include/v8.h:810:26: warning: rvalue references are a C++11 extension 
[-Wc++11-extensions] 
V8_INLINE Global(Global other) : PersistentBaseT(other.val_) { 
   ^ 
  include/v8.h:818:40: warning: rvalue references are a C++11 extension 
[-Wc++11-extensions] 
V8_INLINE Global operator=(GlobalS rhs) { 
 ^ 
  include/v8.h:838:21: warning: deleted function definitions are a C++11 
  extension 
[-Wc++11-extensions] 
Global(Global) = delete; 
  ^ 
  include/v8.h:839:29: warning: deleted function definitions are a C++11 
  extension 
[-Wc++11-extensions] 
void operator=(Global) = delete; 
  ^ 
  include/v8.h:786:42: error: use of undeclared identifier 'nullptr' 
V8_INLINE Global() : PersistentBaseT(nullptr) {} 
   ^ 
  include/v8.h:811:18: error: use of undeclared identifier 'nullptr' 
  other.val_ = nullptr; 
   ^ 
  include/v8.h:823:18: error: use of undeclared identifier 'nullptr' 
rhs.val_ = nullptr; 
   ^ 
  include/v8.h:830:44: warning: rvalue references are a C++11 extension 
[-Wc++11-extensions] 
Global Pass() { return static_castGlobal(*this); } 
 ^ 
  include/v8.h:845:26: warning: alias declarations are a C++11 extension 
[-Wc++11-extensions] 
  using UniquePersistent = GlobalT; 
   ^ 
  include/v8.h:1061:52: error: use of undeclared identifier 'nullptr' 
  ScriptOrigin* origin = nullptr)); 
 ^ 
  include/v8config.h:331:48: note: expanded from macro 'V8_DEPRECATE_SOON' 
  #define V8_DEPRECATE_SOON(message, declarator) declarator 
 ^ 
  In file included from hello_world.cpp:1: 
  include/v8.h:1064:30: error: use of undeclared identifier 'nullptr' 
ScriptOrigin* origin = nullptr); 
   ^ 
  include/v8.h:2022:6: warning: scoped enumerations are a C++11 extension 
[-Wc++11-extensions] 
  enum class NewStringType { kNormal, kInternalized }; 
   ^ 
  include/v8.h:2230:42: error: 'v8::NewStringType' is not a class, 
 namespace, 
  or 
 

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

[Michael Hablich]

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 on a new feature designed for 
 V8 embedders, called “V8 extras.” The intent is to allow embedders to write 
 self-hosted (i.e. JavaScript) implementations of various features, with 
 more power and less drawbacks than the existing V8 extensions mechanism. 
 Notably, we are building on top of recent snapshotting work to ensure that 
 the code for V8 extras is included in the snapshot, and so should not have 
 negative impact on context startup time.

 You can see a working, albeit in-progress, example of a V8 extra in this 
 CL https://codereview.chromium.org/1118673002, which uses them to 
 implement readable streams from the Streams Standard. General features on 
 display include:

- The inclusion of the extras via the v8_extra_library_files GYP 
variable
- The use of V8 native functions, such as %CreatePrivateOwnSymbol, in 
the .js files (but see below)
- The use of the extrasExports object to export functions and values 
to the embedder. This object can be accessed through the V8 C++ API with 
v8::Context::GetExtrasExportsObject().

 There are a number of changes we’re still working on implementing before 
 we could comfortably say that this feature is ready:

- We do not want to allow extras direct access to V8 native functions, 
but instead only to a small number of pre-specified ones. The details on 
how to do this are still being worked out, but it will probably involve a 
slight change to the authoring format of the extras files, to become e.g. 
script whose completion value is a function that gets such a utility 
 object 
passed in.
- We need a story for segregating “experimental” extras from shipping 
ones, similar to what is being done in V8 already for harmony features. 
Experimental extras cannot live in the snapshot, since they must be able 
 to 
be turned off at runtime, while shipping ones will be compiled in.
- We eventually want to expose an easy way for the embedder to supply 
functions or values to the extras code. This is not actually needed for 
streams, but for example if we were to implement something like 
 TextEncoder 
or URL as an extra, it would be crucial.

 Overall though, we are quite excited about the possibilities this opens 
 up, by allowing embedders a performant way to implement features in 
 JavaScript.

 Best,

 Domenic Denicola
 Jochen Eisinger
 Yang Guo


-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

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 any questions, feel free to contact me.

Cheers,
Michael

On Thursday, May 7, 2015 at 8:02:01 PM UTC+2, Alexis Ménard wrote:

 Hi,

 As noted on blink-dev there is an existing implementation on V8 shipping 
 for over a year now.

 https://github.com/crosswalk-project/v8-crosswalk/commits/master - Please 
 feel free to reuse the existing implementation.

 There is an IA implementation for CrankShaft and TurboFan, and I know that 
 our Intel developers would love to participate in adding SIMD.js support 
 upstream and help you in any way possible.

 If you want please contact us.

 On Thursday, May 7, 2015 at 5:56:56 AM UTC-3, Andreas Rossberg wrote:

 On 7 May 2015 at 02:08, Bill Budge bbu...@google.com wrote:

 # Contact Info
 bbu...@chromium.org, bradnel...@chromium.org

 # TC39 acceptance 

 SIMD.js is a proposal in ES7
 https://github.com/tc39/ecma262

 John Mccutchan’s Strawman proposal (polyfill is spec):
 https://github.com/johnmccutchan/ecmascript_simd 


 # Interest from other vendors 

 Mozilla has implemented this in Firefox:
 https://hacks.mozilla.org/2014/10/introducing-simd-js/

 https://blog.mozilla.org/javascript/2015/03/10/state-of-simd-js-performance-in-firefox/

 Microsoft has announced plans to implement SIMD.js in Chakra, their 
 Javascript engine.
 Slides:  http://channel9.msdn.com/Events/Build/2015/2-763
 Video: http://video.ch9.ms/sessions/build/2015/2-763-LG.mp4

 SIMD.js discussion starts at minute 45:35 and demoed with Mandelbrot at 
 time 49:00.

 # Technical considerations 

 Implementing SIMD should have a small impact on code complexity in V8. 
 There are lots of
 SIMD types and operations but they are very regular.


 # Implementation/testing 

 Design Document to come.


 Note that a proper design doc is a prerequisite for signing off on an 
 intent-to-implement. In particular, I expect that working out such a 
 document will very quickly rectify the above statement about the impact on 
 code complexity.

 /Andreas



-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[v8-users] New handling of MIPS ports

[Michael Hablich]

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 done by the V8 dev*
No action from the MIPS team needed.

*More complicated changes are done by the MIPS team (as before)*
The MIPS team will get CC'ed to the CLs which need their attention in time 
so a patch can be provided *before* the CL lands. The preferred way to 
provide a patch is via an own CL. The V8 team will merge the patch into the 
original CL.

*A mailing list for the MIPS team is provided*
The mailing list v8-mips-ports.at.googlegroups.com will be CC'ed in order 
to contact the whole MIPS team.

*TL;DR;*
*What do I have to do if I am a V8 dev?*
Port yourself OR put v8-mips-ports.at.googlegroups.com on CC of your CL 
before it lands. Wait for the patch and apply it. Land CL.
*What do I have to do if I am a MIPS dev?*
Wait until a port request is send to you. Provide patch via own CL. Add 
link of patch CL to original CL.

This info can also be found 
at: https://code.google.com/p/v8-wiki/wiki/HandlingOfMIPSPorts

If you have any questions please do not hesitate to contact me.

Cheers,
Michael

-- 
-- 
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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Hablich]

Hey v8-users,

we're making big changes to the api (again).  We've found that our api makes 
it extremely difficult to write exception safe code.

*Reference issue*
https://code.google.com/p/v8/issues/detail?id=3929

*Further description*
Consider the following:

LocalValue x = some_value;
s = x.ToString();
// in the current context, ToString might throw an exception, run out
of stack space, whatever...
// if that happens we just return an empty LocalString
s-Anything() // Crash!

There's too much implicit stuff happening here, and it's bad.  It's especially 
bad if you use threads and rely on TerminateExecution(), which causes lots 
of v8 function to return empty handles unexpectedly.

To fix this, we will begin adding functions whose signature makes it impossible 
to make this mistake and we will deprecate and eventually remove all old 
functions.  The new functions will in general come in
two flavours:

functions like:
LocalString ToString(Isolate*);

will become:
MaybeLocalString ToString(LocalContext);

and functions like:
double NumberValue();

will become:
Maybebool NumberValue(LocalContext);

The Maybe values ensure at compilation time that the value returned is checked 
by the embedder, and the explicit Context makes it clear that a context is 
actually required and that javascript may be executed in that context.

*Timeline*
We will add the new API parts gradually to the codebase. When this is 
finished there will be approx. 6 weeks of time where the old and the new 
API will exist side-by-side. This is a good time to make the adjustments in 
your embedding code. After this period the old API will get removed.

We apologize in advance for any trouble this may cause, but we're positive 
that this change will reduce crash rates for practically all v8 embedders.

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 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.