Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

[Jochen Eisinger]

If you build for x87, mips (big endian), ppc, or s390, use gyp, the rest is
on gn.

On Tue, Oct 18, 2016 at 11:04 PM Zac Hansen <xax...@gmail.com> wrote:

> How do I find out what the current supported build process is for a
> platform?   I've been told "if gn doesn't work, use gyp, because it's
> supported until gn works on a platform".. but when neither works, I don't
> know which to ask about how to use.
>
> Thank you for all your help.
>
> --Zac
>
> On Tue, Oct 18, 2016 at 12:49 PM, Jochen Eisinger <joc...@chromium.org>
> wrote:
>
> I tried to fix this here but concluded it's "not supported":
> https://codereview.chromium.org/22382003/
>
> On Tue, Oct 18, 2016 at 9:33 AM Zac Hansen <xax...@gmail.com> wrote:
>
> "component build" = dylib?
>
> It's always worked fine - but this error is new.
>
> Linking against the static version takes forever, so dylibs are the only
> way to go.
>
> On Tue, Oct 18, 2016 at 12:31 AM, Jochen Eisinger <joc...@chromium.org>
> wrote:
>
> I'm surprised that the component build with gyp on mac ever worked for
> you, it never did for me :-/
>
> On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen <xax...@gmail.com> wrote:
>
> manually copying the file into /usr/local/lib works.   Someone said it
> might have to do with the "install_name" being /usr/local/lib, but I don't
> really understand what this means.
>
> Also, it seems broken that copying a file into /usr/local is required for
> part of the build.
>
> --Zac
>
>
> On Monday, October 17, 2016 at 8:02:34 PM UTC-7, Zac Hansen wrote:
>
> I've been successfully building v8 for quite a while and recently pulled a
> new version and am getting the following error on os x el capitan:
>
> make library=shared snapshot=off x64.debug -j2
>
>   ACTION src_v8_gyp_v8_base_target_run_mkpeephole
> /Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc
>
> dyld: Library not loaded: /usr/local/lib/libv8_libbase.dylib
>
>   Referenced from: /Users/xaxxon/v8/out/x64.debug/mkpeephole
>
>   Reason: image not found
>
> /bin/sh: line 1: 18072
> <https://maps.google.com/?q=18072=gmail=g> Trace/BPT trap: 5
>   "/Users/xaxxon/v8/out/x64.debug/mkpeephole"
> "/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc"
>
> make[1]: ***
> [/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc]
> Error 133
>
> make: *** [x64.debug] Error 2
>
> I try setting my DYLD_LIBRARY_PATH to the recently build dylib but that
> doesn't seem to help and it still complains about it not being in
> /usr/local/lib...
>
> Any suggestions?
>
> --
> --
> 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/4aBZYlnpYiM/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.
>
> --
> --
> 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/4aBZYlnpYiM/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.
>
>
> --
> --
> v8-users mailing list
> v8-users@goo

Re: [v8-users] 18n support flags with gn build

[Jochen Eisinger]

I haven't tried this myself yet, but you should be able to use the system
icu by following the steps outlined here:
https://cs.chromium.org/chromium/src/build/linux/unbundle/README for icu.

On Mon, Oct 17, 2016 at 7:25 PM Temuri Imnaishvili 
wrote:

> Hi,
>
> There's this page: https://github.com/v8/v8/wiki/i18n%20support.
>
> What's the equivalent of use_system_icu=1 flag for gn builds?
>
> 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.

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

[Jochen Eisinger]

I'm surprised that the component build with gyp on mac ever worked for you,
it never did for me :-/

On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen  wrote:

> manually copying the file into /usr/local/lib works.   Someone said it
> might have to do with the "install_name" being /usr/local/lib, but I don't
> really understand what this means.
>
> Also, it seems broken that copying a file into /usr/local is required for
> part of the build.
>
> --Zac
>
>
> On Monday, October 17, 2016 at 8:02:34 PM UTC-7, Zac Hansen wrote:
>
> I've been successfully building v8 for quite a while and recently pulled a
> new version and am getting the following error on os x el capitan:
>
> make library=shared snapshot=off x64.debug -j2
>
>   ACTION src_v8_gyp_v8_base_target_run_mkpeephole
> /Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc
>
> dyld: Library not loaded: /usr/local/lib/libv8_libbase.dylib
>
>   Referenced from: /Users/xaxxon/v8/out/x64.debug/mkpeephole
>
>   Reason: image not found
>
> /bin/sh: line 1: 18072
>  Trace/BPT trap: 5
>   "/Users/xaxxon/v8/out/x64.debug/mkpeephole"
> "/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc"
>
> make[1]: ***
> [/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc]
> Error 133
>
> make: *** [x64.debug] Error 2
>
> I try setting my DYLD_LIBRARY_PATH to the recently build dylib but that
> doesn't seem to help and it still complains about it not being in
> /usr/local/lib...
>
> Any suggestions?
>
> --
> --
> 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.

Re: [v8-users] Breaking On Native Function Calls

[Jochen Eisinger]

As far as I know that's not possible. Could you file a feature request for
this (probably on crbug.com if you also want to cover DOM functions)

On Wed, Oct 19, 2016 at 7:38 PM PhistucK  wrote:

> I wanted to know whether there is a V8 (or Chrome) flag of some sort that
> will let me add breakpoints on native function calls.
> I do not mean C++ functions, I mean built in web platform (or ECMAScript)
> functions.
> My issue is that I click on a link and suddenly some code is apparently
> calling document.location.replace("foo") or something and the page
> redirects (maliciously). In order to find the calling code, I want to set a
> breakpoint on calling document.location.replace, which is a native web
> platform function, that is not writable (so I cannot override it with my
> own function using Object.defineProperty, or use a proxy).
> (The code is apparently elusive and obfuscated somewhat, so it is not just
> a search and replace)
> I tried using the Developer Tools API - debug(function), but it did not
> break (even when I call it with setTimeout).
>
> A V8 flag (or a Chrome flag) that either lets me break on calling that
> function, or that overrides the security feature that makes it
> non-writable, or something like that, would let me see the code that calls
> it and find the malicious way it does so.
>
> So, is there something like that?
>
> Thank you!
>
> --
> --
> 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.

Re: [v8-users] ICU options in GN

[Jochen Eisinger]

You have to follow the steps outlined in build/linux/unbundle/README to use
the system icu implementation

On Wed, Oct 19, 2016 at 7:50 PM Andre Cunha 
wrote:

> Hello,
>
> The Building with GYP
>  Wiki page describes
> three ways in which I can use ICU while building v8 with GYP: I can disable
> i18n support altogether (i18nsupport=off), use a custom version of ICU
> (icu_gyp_path=...), or use the system's ICU (use_system_icu=1). However,
> when I build with GN, the only option I can find is disabling i18n support
> (v8_enable_i18n_support=false). I tried passing use_system_icu=1 to GN, but
> I got an error.
>
> So, is it possible to use a custom or the system's ICU with GN?
>
> Thank you,
> Andre
>
> --
> --
> 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.

Re: [v8-users] Re: get error try to get v8 code ,clone depot_tools

[Jochen Eisinger]

This implies that either you don't have an up to date list of trusted root
certificates installed, or there's a proxy somewhere between you and the
internet that intercepts ssl traffic.

In both cases, you need to fix your local network configuration.

On Thu, Oct 20, 2016 at 3:35 AM Zuheng Song  wrote:

> i fellow this wiki to builld v8 , but failed
>
> https://github.com/v8/v8/wiki/Building%20with%20GN
> 
> https://github.com/v8/v8/wiki/Checking%20out%20source
>
> --
> --
> 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.

Re: [v8-users] Re: building v8 fails on bytecode-peephole-table.cc because libv8_libbase.dylib not found

[Jochen Eisinger]

I tried to fix this here but concluded it's "not supported":
https://codereview.chromium.org/22382003/

On Tue, Oct 18, 2016 at 9:33 AM Zac Hansen <xax...@gmail.com> wrote:

> "component build" = dylib?
>
> It's always worked fine - but this error is new.
>
> Linking against the static version takes forever, so dylibs are the only
> way to go.
>
> On Tue, Oct 18, 2016 at 12:31 AM, Jochen Eisinger <joc...@chromium.org>
> wrote:
>
> I'm surprised that the component build with gyp on mac ever worked for
> you, it never did for me :-/
>
> On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen <xax...@gmail.com> wrote:
>
> manually copying the file into /usr/local/lib works.   Someone said it
> might have to do with the "install_name" being /usr/local/lib, but I don't
> really understand what this means.
>
> Also, it seems broken that copying a file into /usr/local is required for
> part of the build.
>
> --Zac
>
>
> On Monday, October 17, 2016 at 8:02:34 PM UTC-7, Zac Hansen wrote:
>
> I've been successfully building v8 for quite a while and recently pulled a
> new version and am getting the following error on os x el capitan:
>
> make library=shared snapshot=off x64.debug -j2
>
>   ACTION src_v8_gyp_v8_base_target_run_mkpeephole
> /Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc
>
> dyld: Library not loaded: /usr/local/lib/libv8_libbase.dylib
>
>   Referenced from: /Users/xaxxon/v8/out/x64.debug/mkpeephole
>
>   Reason: image not found
>
> /bin/sh: line 1: 18072
> <https://maps.google.com/?q=18072=gmail=g> Trace/BPT trap: 5
>   "/Users/xaxxon/v8/out/x64.debug/mkpeephole"
> "/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc"
>
> make[1]: ***
> [/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc]
> Error 133
>
> make: *** [x64.debug] Error 2
>
> I try setting my DYLD_LIBRARY_PATH to the recently build dylib but that
> doesn't seem to help and it still complains about it not being in
> /usr/local/lib...
>
> Any suggestions?
>
> --
> --
> 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/4aBZYlnpYiM/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.
>
> --
> --
> 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.

Re: [v8-users] InternalFieldCount seems to be ignored when ConstructorBehavior is kThrow

[Jochen Eisinger]

could you file a bug including a repro at crbug.com/v8/new please?

thanks
-jochen

On Sat, Nov 26, 2016 at 2:14 AM  wrote:

> When I set the constructor behavior on my FunctionTemplate to kThrow
> (instead of the default kAllow), then create an object from the template
> using InstanceTemplate()->NewInstance(), it seems like the
> InternalFieldCount on the InstanceTemplate is ignored, and the object that
> gets created has 0 internal fields. This only happens when I set the
> constructor behavior to kThrow. Is this a bug? How can I get the object to
> have the right number of internal fields?
>
> ~Theodore
>
> PS: I'm using the version of V8 at branch-heads/5.4.
>
> --
> --
> 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.

Re: [v8-users] Re: What's the correct way to build V8 as a static library on macOS?

[Jochen Eisinger]

with https://codereview.chromium.org/2373783002/ it should be possible to
set v8_static_library to true to get static libraries

On Sat, Nov 26, 2016 at 9:05 AM John Gardner  wrote:

> A tracking issue  at
> Electron's repository confirms that it's not possible to build static
> libraries using GN:
>
> Under gn, there is no way to have v8 build as a standalone static library.
> This is because v8 and other intermediate targets used to build chrome.exe
>  are source_set targets in chrome's gn files .
> These are like virtual targets, and only object (.o) files are ever
> generated for them.
>
>
> A trick described here
>  involves
> modifying *v8/gni/v8.gni* to force static library generation:
>
> template("v8_source_set") {
>  static_library(target_name) {
>
> Which results in these files being included in *out.gn/x64.release/obj/
> * after building with Ninja:
>
>-
>- libfuzzer_support.a
>- libjson_fuzzer.a
>- libparser_fuzzer.a
>- libregexp_fuzzer.a
>- libsimple_fuzzer.a
>- libv8_base.a
>- libv8_external_snapshot.a
>- libv8_libbase.a
>- libv8_libplatform.a
>- libv8_libsampler.a
>- libv8_nosnapshot.a
>- libv8_snapshot.a
>- libwasm_asmjs_fuzzer.a
>- libwasm_fuzzer.a
>
>
>
> On Saturday, 26 November 2016 17:34:00 UTC+11, tbl...@icloud.com wrote:
>
> Actually, that's the wrong link. I've completely forgotten where I found
> out that information.
>
> --
> --
> 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.

Re: [v8-users] v8 gyp for inspector dll configuration fails

[Jochen Eisinger]

I guess https://codereview.chromium.org/2529333002 should fix this

On Thu, Nov 24, 2016 at 7:48 PM iva  wrote:

> Hi,
>
> I am trying to build v8 with the inspector support. The v8 is linked as
> dll. On Windows 10, environment variable set for vs2015. Generator set to
> msvs. I fail at the gyp step when I try to generate solutions with
> inspector enabled (without the inspector everything is fine):
> >python gypfiles\gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library
> -Dv8_enable_inspector=1
> Updating projects from gyp files...
> gyp: Unable to find targets in build file D:\v8\test\debugger\debugger.gyp
> Is there an additional option I must use or any idea of what can the
> problem be?
>
> Regards
>
> --
> --
> 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.

Re: [v8-users] Unable to download V8 on Ubuntu Linux

[Jochen Eisinger]

it looks like the connection to the download servers timed out. Maybe try
again?

On Thu, Nov 10, 2016 at 7:39 AM  wrote:

> Trying to compile V8 for Android. I have Depot Tools, G++ etc all setup
> and running.
>
> The "gclient sync" command seems to exit with an error. On further
> investigation it seems to fail  in several places.
>
> Here are some errors:
>
> 
> 
>
> File
> "/home/sanjit/depot_tools/external_bin/gsutil/gsutil_4.15/gsutil/third_party/httplib2/python2/httplib2/__init__.py",
> line 1018, in connect
> sock.connect((self.host, self.port))
>   File "/usr/lib/python2.7/socket.py", line 228, in meth
> return getattr(self._sock,name)(*args)
> socket.timeout: timed out
> ]
> y", line 228, in meth
> return getattr(self._sock,name)(*args)
> socket.timeout: timed out
> ]
> Downloading 1 files took 1985.098521 second(s)
> Downloading
> /home/sanjit/V8Dev/v8/third_party/binutils/Linux_x64/binutils.tar.bz2
> Traceback (most recent call last):
>   File "v8/third_party/binutils/download.py", line 117, in 
> sys.exit(main(sys.argv))
>   File "v8/third_party/binutils/download.py", line 106, in main
> return FetchAndExtract(arch)
>   File "v8/third_party/binutils/download.py", line 81, in FetchAndExtract
> '-s', sha1file])
>   File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['download_from_google_storage',
> '--no_resume', '--no_auth', '--bucket', 'chromium-binutils', '-s',
> '/home/sanjit/V8Dev/v8/third_party/binutils/Linux_x64/binutils.tar.bz2.sha1']'
> returned non-zero exit status 1
> Error: Command '/usr/bin/python v8/third_party/binutils/download.py'
> returned non-zero exit status 1 in /home/sanjit/V8Dev
> Hook '/usr/bin/python v8/third_party/binutils/download.py' took 1985.19
> secs
>
>
>
>
> Please help !
> Sanjit
>
>
> --
> --
> 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.

Re: [v8-users] libstdc++ from gcc4.6 used to build ICU and v8?

[Jochen Eisinger]

We're working on upgrading the sysroot, however, I'm not aware of any
documentation on how to do that, sorry

On Fri, Nov 11, 2016 at 3:16 PM Jane Chen <jxche...@gmail.com> wrote:

> I now have a test case to confirm that having a mixed std c++ lib of 4.6
> and 4.8 causes my app to crash.  Does v8 support swapping sysroot with
> something else?  If so, where can I find some information in doing so?
>
>
> On Wednesday, November 2, 2016 at 3:48:37 AM UTC-7, Jochen Eisinger wrote:
>
> This is because the sysroot (in build/linux/) is outdated. I filed
> crbug.com/661506 to track this
>
> On Tue, Nov 1, 2016 at 4:41 PM Jane Chen <jxch...@gmail.com> wrote:
>
> I'm investigating a crash in a debug build of our app embedding v8
> 5.3-lkgr and notice libstdc++ from gcc4.6 is included and referenced from
> some of the makefiles to build ICU and v8, although v8 5.3-lkgr requires
> gcc 4.8 or above to build on Linux.  Am I missing something while building
> v8?
>
> Thanks in advance.
>
> --
> --
> 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 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] Compiling 5.4 v8 for Android

[Jochen Eisinger]

I'm not sure, but I think component builds aren't fully supported yet on
5.4, sorry

On Fri, Oct 28, 2016 at 9:25 PM Kevin Read  wrote:

> Hi all,
>
> I'm trying to compile 5.4.500.36 for android using GN. My GN config is:
>
> is_debug=false v8_target_cpu="x86" target_cpu="x86" host_cpu="x64"
> is_clang=true is_component_build=true target_os="android"
> v8_enable_i18n_support=false android_ndk_version="r13"
> android_ndk_major_version="13" v8_use_snapshot=false
>
>
> I use component_build so I can later on create a static library with this
> command (from the obj subdir in the build folder):
>
>
> ~/bin/android-ndk-r13/toolchains/x86-4.9/prebuilt/linux-x86_64/bin/i686-linux-android-
> *ar* rcvs libv8.a v8/*.o v8_base/*.o v8_libbase/*.o v8_libsampler/*.o
> v8_snapshot/*.o v8_libplatform/*.o v8_libsampler/*.o
>
>
> The result compiles and links ok against my code that uses v8, but for x86
> I get these linker errors:
>
> ../../src/api.cc:5532: error: undefined reference to
> 'v8::internal::ReadNatives()'
>
> ../../src/api.cc:5552: error: undefined reference to
> 'v8::internal::DisposeNatives()'
>
> ../../src/base/once.h:95: error: undefined reference to
> 'v8::internal::SetNativesFromFile(v8::StartupData*)'
>
> ../../src/base/once.h:95: error: undefined reference to
> 'v8::internal::SetSnapshotFromFile(v8::StartupData*)'
>
>
> Is it related to me deactivating snapshots? I'd rather not add all the
> code for loading the blobs from assets for now. Should I add
> v8_nosnapshot/*.o instead of v8_snapshot/*.o into the library?
>
>
> Thanks and best,
>
> Kevin
>
>
>
> --
> --
> 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.

Re: [v8-users] How to retain or reacquire v8::ScriptCompiler::Source object?

[Jochen Eisinger]

you can get the ScriptOrigin from a v8::Function via GetScriptOrigin. You
can also ToString a function to get the source, but you could as well
create a global to the source.

On Wed, Oct 12, 2016 at 12:49 AM Zac Hansen  wrote:

> I'd like to keep around the data in a v8::ScriptCompiler::Source object,
> but I see it has v8::Local objects in it, which means I can't just make a
> Global out of it (right?).
>
> Is there some way to reacquire that object later or to keep it around
> indefinitely (outside of a handle scope)?
>
> Thank you.
>
> --Zac
>
> --
> --
> 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.

Re: [v8-users] Temporary ObjectTemplate

[Jochen Eisinger]

depends on what you mean by wrapper. Typically, we'd call a JS object that
corresponds to an embedder object a "wrapper"

On Wed, Oct 12, 2016 at 12:28 AM Zac Hansen <xax...@gmail.com> wrote:

> why wouldn't you just use a v8::External?  Isn't that exactly what they're
> meant for?
>
>
> On Monday, October 10, 2016 at 5:08:54 AM UTC-7, Riccardo Corsi wrote:
>
> will do, thanks!
>
> On Fri, Oct 7, 2016 at 7:19 AM, Jochen Eisinger <joc...@chromium.org>
> wrote:
>
> If possible, reusing the object template will save space, and is preferable
>
> On Thu, Oct 6, 2016 at 8:18 PM Riccardo Corsi <riccard...@kairos3d.it>
> wrote:
>
> Hi all,
>
> I'm using ObjectTemplate to create JS empty objects that are simple
> wrappers of a c++ object
> (in the JS code they are just used as "handles" to pass the objects around
> in the script).
>
> I was just wondering if there is any issue or penalty to use a new
> ObjectTemplate every time (see code below)
> or if I should store the ObjectTemplate in a persistent handle and reuse
> it.
>
> Thank you,
> Ricky
>
> v8::Handle WrapNativeElem(NativeElem* elem)
>{
>   Isolate* isolate = Isolate::GetCurrent();
>   EscapableHandleScope handle_scope(isolate);
>
>   // create an empty object
>   v8::Handle elem_templ = v8::ObjectTemplate::New
> ();
>   elem_templ->SetInternalFieldCount(1);
>   v8::Local wrapper = elem_templ->NewInstance();
>
>   // set the game state as internal field and return the wrapper
>   wrapper->SetInternalField(0, External::New(Isolate::GetCurrent(),
> elem));
>   return handle_scope.Escape(wrapper);
>}
>
>
> --
> --
> 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 a topic in the
> Google Groups "v8-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/v8-users/GQmzqNKKDrQ/unsubscribe.
>
> To unsubscribe from this group and all its topics, 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 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: How to build V8 on Linux using GCC instead of Clang?

[Jochen Eisinger]

I assume that CentOS 7 doesn't have the required libraries to compile the
latest version of V8.

On Tue, Oct 11, 2016 at 4:19 PM Ivan Pizhenko 
wrote:

> Tried this. I have following args.gn
>
> is_debug=true
> is_component_build=true
> target_cpu="x64"
> v8_target_cpu="x64"
> v8_postmortem_support=true
> is_clang=false
> use_sysroot=false
>
>
> and getting this error
>
> Package glib-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `glib-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'glib-2.0' found
> Package gmodule-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gmodule-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gmodule-2.0' found
> Package gobject-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gobject-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gobject-2.0' found
> Package gthread-2.0 was not found in the pkg-config search path.
> Perhaps you should add the directory containing `gthread-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'gthread-2.0' found
> Could not run pkg-config.
>
> I am trying to build on the CentOS 7.
> Updated OS with latest updates, installed package glib-devel.
> What else is missing?
>
>
> 2016-09-28 15:36 GMT+03:00 'Michael Achenbach' via v8-users <
> v8-users@googlegroups.com>:
>
> You need this in your args.gn:
> is_clang=false
> use_sysroot=false
>
>
> On Wednesday, September 28, 2016 at 2:15:47 AM UTC+2, Ivan P. wrote:
>
> Amendment: used ninja -v -C out.gn/test1
> So I can see all commands executed in console output, and I can see it
> uses clang++.
>
> среда, 28 сентября 2016 г., 3:13:02 UTC+3 пользователь Ivan P. написал:
>
> I have set up depot tools and checked out latest stable V8 version from
> latest stable Chromium (V8 ver. 5.3.332.45) like this.
>
> fetch v8
> cd v8
> git checkout -b mybranch 5.3.332.45
> gclient sync
>
> I have generated build files using
>
> gn args gn.out/test1
>
> and run build as
>
> ninja -C gn.out/test1
>
> and I can see that V8 is being built using clang++.
>
> I want to build using g++.
>
> What should be changed, please advise.
>
> --
> --
> 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/l-atCAMVHZU/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.
>
> --
> --
> 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.

Re: [v8-users] Building v8

[Jochen Eisinger]

support for compiling libplatform as a shared library landed a few days
ago. If you compile with the gn flag is_component_build = true, you should
get a shared library

On Sat, Oct 15, 2016 at 10:06 PM Temuri Imnaishvili <temuri...@gmail.com>
wrote:

> Jochen,
>
> Facing the same problem. Can you provide us with help on compiling it
> correctly?
>
> Thanks!
>
>
> On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote:
>
> If you want to build v8 with shared libraries, set the gn arg
> is_component_build=true
>
> Yes, we intend to update the embedder guide. Contributions or bug reports
> are always welcome!
>
> On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors <furious...@gmail.com>
> wrote:
>
> Ok - i'll try and give that a shot. Are there any plans on upgrading the
> Embedded Guide to something more recent than v4.8?
> If I work this out - would I be able to contribute to the wiki to update
> it for everyone else?
>
>
> On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger
> wrote:
>
> by default, we build thin archives which are suitable for static linking
> against other apps, and yes, you will need the .o files around for that.
>
> If you'd rather have shared libraries (.so files), set the gn
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp <furious...@gmail.com> wrote:
>
> I've followed the current instructions for building v8 with GN on
> https://github.com/v8/v8/wiki/Building%20with%20GN but after further
> inspection it looks as if the build only links the .o output instead of
> creating libraries for use in other applications.
>
> Am I missing a step or is this intended? I am trying to use the output
> library in another application.
>
> V8 Build-Head 5.4, Linux x64
>
> --
> --
> 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.
>

-- 
-- 
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] gypfiles/gyp_v8 options to this script

[Jochen Eisinger]

no, the options aren't documented :-/

However, gyp is deprecated, have you looked at gn yet?

On Wed, Dec 7, 2016 at 9:30 AM  wrote:

> Is there anywhere documented what options and values does gypfiles/gyp_v8
>  script take ?
>
> --
> --
> 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.

Re: [v8-users] Looking for streamlined way to access object properties

[Jochen Eisinger]

You could use v8::Object::GetOwnPropertyNames instead of trying each key
individually

On Tue, Dec 6, 2016 at 11:04 PM kent williams 
wrote:

> There's a convention that we use for our C++ native functions called from
> C++, where required arguments are followed (optionally) by an object whose
> properties are additional flags. EG
>
> var num = convertNumber(x);
> var num2 = convertNumber(x, { base: 8 });
>
> Is there a streamlined way to extract properties from this optional object?
>
> I end up doing this:
>
> v8::Local argsObj;
> argsObj.Clear();
> if(args.Length() >=2)
>   argsObj = args[1];
>
> const char *cvval = 0;
> if(!argsObj.IsEmpty()) {
>   v8::Local cvt = v8::String::NewFromUtf8(isolate,
>"convert",
> v8::NewStringType::kNormal).ToLocalChecked();
>   v8::MaybeLocal convertval = argsObj->Get(context,cvt);
>
>   if(!convertval.IsEmpty()) {
> v8::Local cv = convertval.ToLocalChecked();
> v8::String::Utf8Value val2 = cv->ToString();
> cvval = *val2 ? *val2 : 0;
>   }
> }
>
> This seems like a whole lot of work -- way more than Spidermonkey, for
> example.
>
> Are there some convenience functions that make this less painful, or do I
> have to write my own?
>
> 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.

Re: [v8-users] How to compile the samples/hello-world.cc example on ubuntu 64 bit ?

[Jochen Eisinger]

can you build a current version of V8 (using gn/ninja)?

On Fri, Jan 6, 2017 at 8:25 PM <vertabso...@gmail.com> wrote:

> Thank you for your answer Jochen Eisinger, but I tried this and it didn't
> work, of course. I couldn't switch to the 4.8 version of v8, I don't know
> why. Moreover, I would like to compile with an up-to-date version of v8.
>
>
> Le lundi 2 janvier 2017 09:39:30 UTC+1, Jochen Eisinger a écrit :
>
> https://github.com/v8/v8/wiki/Getting%20Started%20with%20Embedding explains
> how to compile the sample
>
> note that if you build all of v8, the hello world sample will be compiled
> automatically
>
> On Sun, Dec 25, 2016 at 8:39 PM <verta...@gmail.com> wrote:
>
> Hello everyone,
>
> I am new to v8. I am trying to achieve something that should be easy, but
> I just can't get it right.
>
> I have downloaded v8 via depot-tools and built it via make x64, and now I
> am trying to compile the hello-world example which is given in the
> "samples" folder.
> What command am I supposed to type in ubuntu terminal for this to work,
> please ?
>
> I have tried g++ hello-world.cc -o hello -I. but that fails with the
> following error :
>
> In file included from hello-world.cc:9:0:
> include/libplatform/libplatform.h:8:44: fatal error:
> libplatform/libplatform-export.h: No such file or directory
> compilation terminated.
>
> Thank you.
>
> --
> --
> 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 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 with MSVC & GN - Where do the static files go?

[Jochen Eisinger]

With the latest dev version of V8 (5.7), you should be able to get static
libraries using the gn flag v8_static_library = true

On Tue, Jan 10, 2017 at 4:26 PM Hans Maier  wrote:

> Hi,
>
> I had the same issue. I ended up creating the static libs from the
> obj-files using the MSVC lib tool manually.
>
> Unsatisfactory, but it was working for me.
>
> Am Montag, 9. Januar 2017 15:55:40 UTC+1 schrieb Brendan Bates:
>
> Hello,
>
> I have seen this issue pop up a couple times on here and wondering what
> the current status is.  I was spending the morning trying to get ahead of
> the game and switch from a Gyp build to a GN build.  We are using MSVC 2015
> to perform the build.  I am successfully configuring and building using the
> following commands:
>
> > gn gen out/x86.debug --args="is_debug=true v8_use_snapshot=false
> target_cpu=\"x86\" disable_libfuzzer=true"
> Done. Made78 targets from 44 files in 1900ms
>
> > ninja-C out/x86.debug d8
> ninja: Entering directory `out.gn/x86.debug'
> [49/886] LINK mkpeephole.exe mkpeephole.exe.pdb
> LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/OPT:ICF'
> specification
> [886/886] LINK d8.exe d8.exe.pdb
> LINK : warning LNK4075: ignoring '/INCREMENTAL' due to '/OPT:ICF'
> specification
>
> The build results are confusing, however.  In the "out" directory, I find
> the v8.dll, along with the icu*.dll files.  What seems to be missing are
> the static .lib files that were necessary in previous builds
> (v8_libbase.lib, v8_libplatform.lib and v8_nosnapshot.lib).  My build with
> new new v8 DLL does not seem to work without these.  So I attempted a
> static build, by adding the GN argument `is_component_build=false`.  To my
> surprise, no static libraries were generated at all!  Is this something
> that is planning on being supported in the future?  If not, what is the way
> around this?  I certainly don't want to transition my project to use GN.
> Thoughts?  Thanks in advance.
>
> --
> --
> 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.

Re: [v8-users] Segfault calling v8::Persistent::Reset.

[Jochen Eisinger]

Can you reproduce this and catch it in a debugger? Or run with ASAN enabled?

On Fri, Dec 2, 2016 at 2:18 AM Jane Chen  wrote:

> Embedding v8 5.3.  Seeing a segfault in our stress test:
>
> Critical: #6  0x7fbf3f6c0173 in 
> v8::internal::GlobalHandles::Node::Release() () from lib/libv8.so
>
> This happens when v8::Persistent::Reset is called.
>
> Has anyone else seen this?  Any clues on what might be wrong?
>
> 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.

Re: [v8-users] Re: What's the correct way to build V8 as a static library on macOS?

[Jochen Eisinger]

sorry for the long delay in answering.

I don't know how to control the rpath, maybe asking on gn-...@chromium.org is
an option?

On Mon, Nov 28, 2016 at 11:05 AM John Gardner <gardnerjo...@gmail.com>
wrote:

> Ah awesome, thanks!
>
> Similar question: is it possible to set the rpath at linking-time when
> compiling a component build? It doesn't seem like ldflags can be modified
> from a configuration-level. Perhaps I'm using the wrong approach...
>
> I need each dylib to be compiled with an absolute rpath (specifically,
> /usr/local/opt). Currently, it's attempting to load shared libraries from
> the executable's path, which doesn't work for the intended directory
> arrangement:
>
> lib
> lib/libv8.dylib
> lib/libicuuc.dylib
> lib/libicui18n.dylib
> bin
> bin/v8
>
>
> On Monday, 28 November 2016 20:51:45 UTC+11, Jochen Eisinger wrote:
>
> with https://codereview.chromium.org/2373783002/ it should be possible to
> set v8_static_library to true to get static libraries
>
> On Sat, Nov 26, 2016 at 9:05 AM John Gardner <gardne...@gmail.com> wrote:
>
> A tracking issue <https://github.com/electron/electron/issues/7940> at
> Electron's repository confirms that it's not possible to build static
> libraries using GN:
>
> Under gn, there is no way to have v8 build as a standalone static library.
> This is because v8 and other intermediate targets used to build chrome.exe
>  are source_set targets in chrome's gn files <https://goo.gl/VM4xOk>.
> These are like virtual targets, and only object (.o) files are ever
> generated for them.
>
>
> A trick described here
> <https://groups.google.com/forum/#!topic/v8-users/Y05xPj956Ys> involves
> modifying *v8/gni/v8.gni* to force static library generation:
>
> template("v8_source_set") {
>  static_library(target_name) {
>
> Which results in these files being included in *out.gn/x64.release/obj/
> <http://out.gn/x64.release/obj/>* after building with Ninja:
>
>-
>- libfuzzer_support.a
>- libjson_fuzzer.a
>- libparser_fuzzer.a
>- libregexp_fuzzer.a
>- libsimple_fuzzer.a
>- libv8_base.a
>- libv8_external_snapshot.a
>- libv8_libbase.a
>- libv8_libplatform.a
>- libv8_libsampler.a
>- libv8_nosnapshot.a
>- libv8_snapshot.a
>- libwasm_asmjs_fuzzer.a
>- libwasm_fuzzer.a
>
>
>
> On Saturday, 26 November 2016 17:34:00 UTC+11, tbl...@icloud.com wrote:
>
> Actually, that's the wrong link. I've completely forgotten where I found
> out that information.
>
> --
> --
> 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 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] How to compile the samples/hello-world.cc example on ubuntu 64 bit ?

[Jochen Eisinger]

https://github.com/v8/v8/wiki/Getting%20Started%20with%20Embedding explains
how to compile the sample

note that if you build all of v8, the hello world sample will be compiled
automatically

On Sun, Dec 25, 2016 at 8:39 PM  wrote:

> Hello everyone,
>
> I am new to v8. I am trying to achieve something that should be easy, but
> I just can't get it right.
>
> I have downloaded v8 via depot-tools and built it via make x64, and now I
> am trying to compile the hello-world example which is given in the
> "samples" folder.
> What command am I supposed to type in ubuntu terminal for this to work,
> please ?
>
> I have tried g++ hello-world.cc -o hello -I. but that fails with the
> following error :
>
> In file included from hello-world.cc:9:0:
> include/libplatform/libplatform.h:8:44: fatal error:
> libplatform/libplatform-export.h: No such file or directory
> compilation terminated.
>
> Thank you.
>
> --
> --
> 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.

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

[Jochen Eisinger]

hey,

to build for android, you should add target_os = "android" and target_cpu =
"arm".

you'll also have to add target_os = ['android', 'mac'] to your .gclient
file (which should be one level up from your v8 checkout), so gclient sync
will download the android specific deps

hth
-jochen

On Thu, Dec 22, 2016 at 5:41 PM 'Mindy DelliCarpini' via v8-users <
v8-users@googlegroups.com> wrote:

> Need a V8 build for our prototyping tool (boom.googleplex.com). The tool
> runs with a Mac simulator, so the build has to be completed on a Mac.
>
> The TOT v8 builds are broken for Mac, and also for building static full
> libraries (no the thin .a files, which wouldn't be shareable)
>
> I'm interested in getting any of the following working (preference for Mac
> build, but I know its not a common thing)
>
> 1) *Build v8 on my mac*
> Tried old instructions, but failed with missing libraries (standard c++?)
> https://github.com/v8/v8/wiki/D8-on-Android
> Tried new instructions:
> tools/dev/v8gen.py arm.release
> Added: target_os=arm
> Getting this failure:
>
> /Users/mindyp/local/src/v8/buildtools/mac/gn
> --root=/Users/mindyp/local/src/v8 -q --check gen .
>
> ERROR Unresolved dependencies.
>
> //:run_mkpeephole(//build/toolchain/android:android_arm)
>
>   needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)
>
> //:run_mksnapshot(//build/toolchain/android:android_arm)
>
>   needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)
>
>
> 2) *Full static library build on Linux that is not just the .a, so I can
> transfer it to my mac*
> Followed:
> http://linuxplayer.org/2013/12/how-to-build-v8-static-library
> But this breaks during the LD phase
> Added: https://bugs.chromium.org/p/v8/issues/detail?id=5617#c1
>  (LDFLAGS=-lc++)
> Still broken
>
> --
> --
> 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.

Re: [v8-users] Cryptic out-of-memory error

[Jochen Eisinger]

Thank you for the detailed bug report.

I tried reproducing this on the latest version of V8, but couldn't observe
the behavior you described.

Have you considered updating to at least the latest stable version of V8?

On Wed, May 10, 2017 at 7:50 PM Andre Cunha 
wrote:

> I've managed to reproduce the problem using just V8's hello_world example
> (source code attached). I just added a loop around the creation and
> destruction of the Isolate (this is what happens in each cycle of my stress
> test). When I run the process and monitor it in "top", the RES column stays
> constant at around 26 MB, but the VIRT column grows indefinitely; after
> about 7 minutes, the VIRT column reaches around 33 GB, and the process
> crashes (the value of "CommitLimit" in my machine, got from /proc/meminfo,
> is 35,511,816 kB).
>
> Following Michael's suggestion, I changed file src/heap/spaces.cc so that
> it prints a stack trace when it's about to return NULL. I'm also sending
> the stack trace attached. I use V8 5.6.326.42 in Fedora 25, x86_64.
>
> Just to explain why I'm doing this test: in the library I'm working on,
> the user can create a certain kind of thread and send requests to it. Each
> thread needs to run JS code (received from the user), so it creates its own
> Isolate when it needs to, and destroys it when the Isolate is no longer
> necessary. One of our stress tests involves the constant creation and
> destruction of such threads, as well as constantly sending requests to the
> same thread. It was in this context that I found this problem.
>
> On Monday, May 8, 2017 at 12:50:37 PM UTC-3, Andre Cunha wrote:
>>
>> @Michael Lippautz, I'll try adding a breakpoint if AllocateChunk returns
>> NULL; hopefully, I'll get more information about the problem.
>>
>> @Jakob Kummerow, yes, I'm calling Isolate::Dispose() in every isolate
>> after using it. I'll also observe the VIRT column and see if it shows any
>> abnormality.
>>
>> Thank you!
>>
>> On Monday, May 8, 2017 at 11:07:44 AM UTC-3, Jakob Kummerow wrote:
>>>
>>> My guess would be an address space leak (should show up in the "VIRT"
>>> column of "top" on Linux). Are you calling "isolate->Dispose()" on any
>>> isolate you're done with?
>>>
>>> On Mon, May 8, 2017 at 4:01 PM, Michael Lippautz 
>>> wrote:
>>>
 V8 usually fails there if it cannot allocate a 512KiB page from the
 operating system/

 You could try hooking in AllocateChunk [1] and see why it is returning
 NULL and trace back through the underlying calls.

 Best, Michael

 [1]:
 https://cs.chromium.org/chromium/src/v8/src/heap/spaces.cc?q=AllocateChunk=package:chromium=739

 On Mon, May 8, 2017 at 3:27 PM Andre Cunha 
 wrote:

> Hello,
>
> I have embedded v8 into a project for the company I work for, and
> during some stress tests, I've encountered a weird out-of-memory error.
> After considerable investigation, I still have no idea of what might be
> going on, so I'm reaching out to you in hope of some insight.
>
> So here is a summary of the scenario: in each test iteration, I create
> an Isolate, run some short JS code fragments, and then destroy the 
> isolate.
> After the execution of each code fragment, I perform some variable
> manipulations from my C++ code using V8's API, prior to running the next
> fragment. I repeat thousands of such iterations over the same input (it's
> valid), and I expect no memory leaks and no crashes. However, after about 
> 3
> hours, V8 crashes with an out-of-memory error of no apparent reason.
>
> I have run the code though valgrind and using address sanitizing, and
> no memory leaks were detected. Additionally, I monitor memory consumption
> throughout the test; the program's memory usage is stable, without any
> peak, and when V8 crashes the system has a lot of available memory (more
> than 5 Gib). I have used V8's API to get heap usage statistics after each
> successful iteration; the values are always the same, and are shown below
> (they are included in an attached file, typical_memory.txt):
>
> ScriptEngine::Run: finished running at 2017-05-05T13:20:34
>   used_heap_size   : 46.9189 Mib
>   total_heap_size  : 66.1562 Mib
>   Space 0
> name   : new_space
> size   : 8 Mib
> used_size  : 2.47314 Mib
> available_size : 5.39404 Mib
>   Space 1
> name   : old_space
> size   : 39.5625 Mib
> used_size  : 31.6393 Mib
> available_size : 5.51526 Mib
>   Space 2
> name   : code_space
> size   : 10.4375 Mib
> used_size  : 6.16919 Mib
> available_size : 0 B
>   Space 3
> name   : map_space
> 

Re: [v8-users] Adding Signature to my FunctionTemplate but "derived types" calling functions get Illegal Invocation errors

[Jochen Eisinger]

I recently updated the documentation for Info.Holder() and Info.This() -
they only differ if you use a hidden prototype.

The comment on Signature you quoted is correct - your example code doesn't
use inheritance of the FunctionTemplate but JS inheritance.

On Mon, May 29, 2017 at 9:08 AM Zac Hansen <xax...@gmail.com> wrote:

> My understanding is that the signature picking out the object in the
> prototype chain was the difference between info.This and info.Holder.
> Mostly from reading the thread I linked previously.
>
> Also, this is from the doxygen docs for signature:
>
> > A receiver matches a given signature if the receiver (or any of its
> hidden prototypes) was created from the signature's FunctionTemplate
> <http://v8.paulfryzel.com/docs/master/classv8_1_1_function_template.html>,
> or from a FunctionTemplate
> <http://v8.paulfryzel.com/docs/master/classv8_1_1_function_template.html> that
> inherits directly or indirectly from the signature's FunctionTemplate
> <http://v8.paulfryzel.com/docs/master/classv8_1_1_function_template.html>.
>
>
> On Mon, May 29, 2017 at 12:01 AM, Zac Hansen <xax...@gmail.com> wrote:
>
>> In this thread:
>> https://groups.google.com/forum/#!topic/v8-users/Axf4hF_RfZo
>>
>> it says:
>>
>> > If your function has a signature that says that it must be called on a
>> particular type v8 will search the prototype chain for an object of
>> that type when the function is called.
>>
>>
>> Given my code, I don't understand why making an object that directly sets
>> its prototype as an object capable of calling a function with a signature
>> wouldn't be able to call that same function.
>>
>> Is that thread I linked wrong?   Or am I misunderstanding something?
>>
>> On Sun, May 28, 2017 at 11:57 PM, Jochen Eisinger <joc...@chromium.org>
>> wrote:
>>
>>> A signature requires the object either be constructed from the same
>>> FunctionTemplate (as e.g. new MyType() does), or from a FunctionTemplate
>>> that inherited from the signature's FunctionTemplate.
>>>
>>> Note however that the "info.Holder" would still point at the receiver,
>>> and not the prototype with the matching signature :/
>>>
>>> On Sun, May 28, 2017 at 7:27 PM Zac Hansen <xax...@gmail.com> wrote:
>>>
>>>> I create a "constructor" FunctionTemplate, create a signature from that
>>>> FunctionTemplate, then on that FunctionTemplate's PrototypeObject
>>>> ObjectTemplate, I create a bunch of FunctionTemplate's using the signature
>>>> I generated before.
>>>>
>>>> I can call the function with objects created directly from the
>>>> "constructor" FunctionTemplate.  But if I call it from an object with that
>>>> object in the prototype chain, it doesn't work.
>>>>
>>>> base = new MyType();
>>>> derived = Object.create(base);  // setting .__proto__ has the same
>>>> behavior
>>>>
>>>> base.some_native_function(); <== works
>>>>
>>>> derived.some_native_function(); <== TypeError: Illegal invocation
>>>>
>>>>
>>>>
>>>> Anyone know what I might be doing wrong?  If I remove the signature,
>>>> everything works fine, but then holder == this when calling with derived,
>>>> which isn't what I want.
>>>>
>>>> --Zac
>>>>
>>>> --
>>>> --
>>>> 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/dR8oI0ZwzG0/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.
>>>
>>
>>
> --
> --
> 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.

Re: [v8-users] Adding Signature to my FunctionTemplate but "derived types" calling functions get Illegal Invocation errors

[Jochen Eisinger]

A signature requires the object either be constructed from the same
FunctionTemplate (as e.g. new MyType() does), or from a FunctionTemplate
that inherited from the signature's FunctionTemplate.

Note however that the "info.Holder" would still point at the receiver, and
not the prototype with the matching signature :/

On Sun, May 28, 2017 at 7:27 PM Zac Hansen  wrote:

> I create a "constructor" FunctionTemplate, create a signature from that
> FunctionTemplate, then on that FunctionTemplate's PrototypeObject
> ObjectTemplate, I create a bunch of FunctionTemplate's using the signature
> I generated before.
>
> I can call the function with objects created directly from the
> "constructor" FunctionTemplate.  But if I call it from an object with that
> object in the prototype chain, it doesn't work.
>
> base = new MyType();
> derived = Object.create(base);  // setting .__proto__ has the same behavior
>
> base.some_native_function(); <== works
>
> derived.some_native_function(); <== TypeError: Illegal invocation
>
>
>
> Anyone know what I might be doing wrong?  If I remove the signature,
> everything works fine, but then holder == this when calling with derived,
> which isn't what I want.
>
> --Zac
>
> --
> --
> 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.

Re: [blink-dev] Re: [v8-users] Intent to Ship: Optional catch binding

[Jochen Eisinger]

I thought V8 wanted to use the blink process nowadays?

On Thu, Jan 18, 2018 at 10:32 PM Adam Klein  wrote:

> LGTM!
>
> Note that this is a v8/JavaScript feature, so this is just an FYI for
> blink-dev at the moment.
>
> On Thu, Jan 18, 2018 at 12:19 PM, Sathya Gunasekaran  > wrote:
>
>> Contact Emails:
>> gsat...@chromium.org
>> bak...@gmail.com
>>
>> Spec:
>> https://tc39.github.io/proposal-optional-catch-binding/
>>
>> Summary:
>> This proposal allows developers to use try/catch without creating an
>> unused binding.
>>
>> Interoperability and Compatibility Risk:
>> This is a stage3 feature. Previously not having a binding was an error,
>> so there's no compat risk.
>>
>> Firefox 58 Beta and Safari Tech Preview 37 ship this feature. Edge has
>> not implemented this yet.
>>
>> V8 tests as well as test262 tests pass.
>>
>> Tracking bug:
>> https://bugs.chromium.org/p/v8/issues/detail?id=6889
>>
>> Chromestatus entry:
>> https://www.chromestatus.com/features/5810795665424384
>>
>> --
>> --
>> 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.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEvLGcJL74s7xeQLU%2BMC3MCYoUnyKzSLGF5-Jhbo5%2BJj9i%2B3iQ%40mail.gmail.com
> 
> .
>

-- 
-- 
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-team] [v8-status-updates] Intent to ship: module namespace exports

[Jochen Eisinger]

v8-status-updates to BCC

Please don't mix internal and external mailing lists

Sathya Gunasekaran  schrieb am Mo., 15. Okt. 2018,
06:22:

> LGTM
> On Mon, Oct 15, 2018 at 2:58 PM Georg Neis  wrote:
> >
> > Summary
> > This feature extends the existing syntax for module exports by the form
> >   export * as foo from "bar"
> > which is the analogue to the existing form
> >   import * as foo from "bar"
> > It is equivalent to
> >   import * as _foo from "bar"; export {_foo as foo}
> > except that it does not introduce a local name (here _foo).
> >
> > Specification
> > https://github.com/tc39/ecma262/pull/1174
> >
> > Contact
> > n...@chromium.org
> >
> > Chrome status entry
> > https://www.chromestatus.com/feature/6439734029058048
> >
> > V8 tracking bug
> > https://bugs.chromium.org/p/v8/issues/detail?id=8101
> >
> > Interoperability and compatibility risk
> > No risks as this is new syntax that results in a syntax error when not
> supported.
> >
> > Is this feature fully tested?
> > Yes, by own (V8) tests as well as Test262 tests.
> >
> > Requesting approval to ship?
> > Yes. Note that since this is a V8/JS feature, this post is just an FYI
> to blink-dev — no signoff from Blink API owners is required.
> >
> > --
> > Georg Neis
> > Software Engineer
> >
> > Google Germany GmbH
> > Erika-Mann-Straße 33
> > 80636 München
> >
> > Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
> > Registergericht und -nummer: Hamburg, HRB 86891
> > Sitz der Gesellschaft: Hamburg
> >
> > Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise erhalten
> haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter,
> löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen,
> dass die E-Mail an die falsche Person gesendet wurde.
> >
> > This e-mail is confidential. If you received this communication by
> mistake, please don't forward it to anyone else, please erase all copies
> and attachments, and please let me know that it has gone to the wrong
> person.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "V8 status emails and design docs" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to v8-status-updates+unsubscr...@google.com.
> > To post to this group, send email to v8-status-upda...@google.com.
> > To view this discussion on the web visit
> https://groups.google.com/a/google.com/d/msgid/v8-status-updates/CABT__oFbT23Qh0g9idTfox5_bHr1gDUepYW134yv9iTS4RUubw%40mail.gmail.com
> .
> >
> > --
> > v8-team mailing list
> > v8-t...@google.com
> > https://groups.google.com/a/google.com/group/v8-team
>
> --
> --
> 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.