Ah, the C++14/17 connection didn't occur to me -- that isn't crazy. (It's
decidedly inconvenient for non-Chromium users, but not crazy :-)
On Tue, Mar 19, 2019 at 3:03 AM Ben Noordhuis wrote:
> On Tue, Mar 19, 2019 at 2:02 AM 'Steven Johnson' via v8-users
> wr
Are the details of how `use_custom_libcxx` should be set documented
anywhere? It appears that the default for the `x64.optdebug` and
`x64.debug` builds is to set this to true; this can cause amusing crashes
if you link the resulting dynamic library into an executable that is linked
against the
od thing for my purposes, as
having a linker step will address some other issues on my plate._
Sorry for the noise.
On Tue, Feb 26, 2019 at 11:45 AM Ben Noordhuis wrote:
> On Tue, Feb 26, 2019 at 2:12 AM 'Steven Johnson' via v8-users
> wrote:
> > I'm experimenting w
On Mon, Feb 25, 2019 at 5:28 PM J Decker wrote:
> I'm not familiar with these, but do know about HEAP8, HEAP32, etc. :) The
> code I get generated does not have either of those symbols; it might be to
> support some C++ structure you have... All the code I compiled was actually
> C. The basic C
I'm experimenting with embedding V8 in a test app in order to load,
compile, and run wasm bytecode that has been generated by LLVM (using V8
7.4.x and recent trunk versions of LLVM)
Loading and running seems simple enough
(via WasmModuleObject::DeserializeOrCompile), but calling the resulting
