android-node-v8.git - Fork of Node.JS that build on Android

Age	Commit message (Collapse)	Author
2018-12-06	tools: prepare tools/genv8constants.py for Python 3	cclauss
	PR-URL: https://github.com/nodejs/node/pull/24801 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
2018-11-25	tools: use print() function on both Python 2 and 3	cclauss
	PR-URL: https://github.com/nodejs/node/pull/24486 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2018-10-09	benchmark,doc,lib,src,test,tools: fix typos	Brandon Smith
	PR-URL: https://github.com/nodejs/node/pull/23302 Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
2017-10-14	tools: minor performance improvement	Anna Henningsen
	PR-URL: https://github.com/nodejs/node/pull/16125 Reviewed-By: Anna Henningsen <anna@addaleax.net>
2013-03-20	dtrace: fix generation of v8 constants on freebsd	Fedor Indutny
	Every constant is certainly 4 bytes now, but freebsd's objdump utility prints out odd byte sequences (5-bytes, 6-bytes and even 9-bytes long) for v8's data section. We can safely ignore all upper bytes, because all constants that we're using are just `int`s. Since on all supported platforms `int` is 32bit long (and anyway v8's constants are 32bit too), we ignore all higher bits if they were read.
2013-03-20	dtrace: x64 ustack helper	Fedor Indutny

2013-02-26	Revert "sunos: unbreak build after v8 downgrade"	Fedor Indutny
	This reverts commit f80f3c5f62a3955636c1af1872ef9539a0b01cb0.
2013-02-26	sunos: unbreak build after v8 downgrade	Ben Noordhuis
	Commit 3d67f89 ("fix generation of v8 constants on freebsd") is an unfortunate victim of this rollback. Revert "dtrace: fix generation of v8 constants on freebsd" Revert "dtrace: More style" Revert "dtrace: Make D style more D-ish" Revert "dtrace: x64 ustack helper" Revert "dtrace: fix style in ustack helper" Revert "dtrace: SeqAsciiString was renamed to SeqOneByteString in v8" This reverts commit 3d67f895521cf905922d20af9b03e5c73c363868. This reverts commit 321b8eec08d445d60a4149bfa71959936fc189c6. This reverts commit 38df9d51a229e1d74b2d1c2835353f07c784cfc3. This reverts commit f9afb3f01002e5667a0df80ee784af0dfe2305c2. This reverts commit 13296e4b13b5ed192c4faa6501f3efec2ded8ac1. This reverts commit 3b715edda97c8edfd95cc1fb8d31f92cef6bcc52.
2013-01-21	dtrace: fix generation of v8 constants on freebsd	Fedor Indutny
	Every constant is certainly 4 bytes now, but freebsd's objdump utility prints out odd byte sequences (5-bytes, 6-bytes and even 9-bytes long) for v8's data section. We can safely ignore all upper bytes, because all constants that we're using are just `int`s. Since on all supported platforms `int` is 32bit long (and anyway v8's constants are 32bit too), we ignore all higher bits if they were read.
2013-01-08	build: fail w/err msg when missing binutils	Mike Harsch
	Building --with-dtrace requires objdump from GNU binutils. This change inserts a helpful error message if there is a problem executing objdump.
2013-01-07	dtrace: x64 ustack helper	Fedor Indutny

2012-07-18	tools: speed up genv8constants	Dave Pacheco
	genv8constants was much slower than necessary due to lack of pipe buffering.
2012-04-01	build: add support for DTrace and postmortem	Dave Pacheco
	* fixes #2110 * includes V8 postmortem metadata in Solaris builds * adds GYP support for DTrace probes and ustack helper * ustack helper derives constants dynamically from libv8_base.a * build with DTrace support by default on SunOS