duktape

Commit Graph

Author	SHA1	Message	Date
Sami Vaarala	4380b9a80b	Merge pull request #1402 from svaarala/fix-thread-prototype-class Fix incorrect internal class number of Duktape.Thread.prototype	8 years ago
Sami Vaarala	0fd2787612	Releases: Duktape.Thread.prototype class number	8 years ago
Sami Vaarala	cc88be86a4	Fix out-of-sync genbuiltins.py class number	8 years ago
Sami Vaarala	860c4febde	Testcase coverage for Thread.prototype class	8 years ago
Sami Vaarala	e525cbe174	Merge pull request #1401 from svaarala/use-32bit-refcount-default Use a 32-bit refcount field by default	8 years ago
Sami Vaarala	5d119e1674	Releases: 32-bit refcount field	8 years ago
Sami Vaarala	877527e313	Website note on 32-bit refcount	8 years ago
Sami Vaarala	b64588600f	Build changes for 32-bit refcount	8 years ago
Sami Vaarala	75cd2ca812	Internal doc changes for 32-bit refcount	8 years ago
Sami Vaarala	13f1fff5b0	Add support for DUK_USE_REFCOUNT32 (new default)	8 years ago
Sami Vaarala	e4bb928f24	Config option changes for 32-bit refcount default	8 years ago
Sami Vaarala	db1de6850c	Merge pull request #1400 from svaarala/add-incref-wrap-assert Add wrap asserts for INCREF	8 years ago
Sami Vaarala	566d206c34	Releases: INCREF wrap asserts	8 years ago
Sami Vaarala	284c717051	Add wrap asserts for INCREF The refcount field must be chosen so that there's never any wrapping, otherwise memory unsafe behavior will happen. For the default configuration a size_t is used for refcount; it's guaranteed not to wrap because there can't be enough references to wrap it. For low memory targets it's possible to configure 16-bit refcounts. This is fine as long as memory pools are small enough to never contain more than 2^16-1 references.	8 years ago
Sami Vaarala	f81e83fdff	Merge pull request #1385 from svaarala/duk-module-snprintf-msvc Use _snprintf() for pre-MSVC 2015 in extras/module-duktape	8 years ago
Sami Vaarala	79dd8bc7de	Merge pull request #1395 from svaarala/fix-module-loader-last-line Allow modules with // on last unterminated line	8 years ago
Sami Vaarala	971946f37a	Merge pull request #1398 from svaarala/faster-refzero-finalizer-check Faster finalizer existence check in GC	8 years ago
Sami Vaarala	0125e3aa42	Releases: faster finalizer check	8 years ago
Sami Vaarala	13ee812b07	Internal doc updates for finalizer check change	8 years ago
Sami Vaarala	bd77ae2546	Testcase fix for finalizer check change	8 years ago
Sami Vaarala	cfaf5dc796	Use DUK_HOBJECT_FLAG_HAVE_FINALIZER for checks One bottleneck in refzero and mark-and-sweep handling is checking whether an object has an own or inherited _Finalizer property. This check walked the prototype chain and did a property lookup for every object. Because a finalizer is usually not present, the prototype chain would almost always be walked to completion. Improve this behavior by: * Adding a DUK_HOBJECT_FLAG_HAVE_FINALIZER flag. The flag is set when the object has an own _Finalizer property with a callable value, and cleared otherwise. The flag is only set by duk_set_finalizer(), so any other means of changing the internal _Finalizer property will leave the flag out of sync (which causes a finalizer run to be skipped). * Adding duk_hobject_has_finalizer_fast() which checks for finalizer existence by walking the prototype chain, but only checking the flag, not the property table. * Use the fast finalizer check in refzero and mark-and-sweep. Out-of sync cases: * If the flag is set but there is no actual finalizer, the object will go through finalizer processing when garbage collecting. This is harmless: the finalizer call will fail and the object will be garbage collected, but with some potential delay (especially for mark-and-sweep). * If the flag is cleared but there is an actual finalizer, the finalizer will be ignored. Related changes: * When duk_dump_function() is called, zero DUK_HOBJECT_FLAG_HAVE_FINALIZER on serialization, so it won't be set when the function is loaded back. If this is not done, the loaded function will (harmlessly) go through finalizer processing when garbage collected. * Update debugger artificial properties to include "have_finalizer" flag. Other changes: * A few DUK_UNLIKELY() attributes for prototype sanity limits which are almost never hit.	8 years ago
Sami Vaarala	6e44372c26	Releases: modules with trailing // comment	8 years ago
Sami Vaarala	d5f1a647e1	Allow modules with // on last unterminated line	8 years ago
Sami Vaarala	3e7cec9cb1	Merge pull request #1393 from svaarala/releases-windows-tzoffset-simplify Releases: simplify Windows tzoffset (nodst)	8 years ago
Sami Vaarala	b91ee63773	Releases: simplify Windows tzoffset (nodst)	8 years ago
Sami Vaarala	0217f0f01e	Merge pull request #1389 from beevik/simplify-tzoffset Simplify calculation in duk_bi_date_get_local_tzoffset_windows_no_dst	8 years ago
Sami Vaarala	ce82738e7e	Merge pull request #1392 from svaarala/apidoc-push-heapptr-finalizer-note Clarify duk_push_heapptr() and finalizer calls	8 years ago
Sami Vaarala	f4f39b32c8	Clarify duk_push_heapptr() and finalizer calls	8 years ago
Sami Vaarala	cefa38fabd	Merge pull request #1390 from svaarala/fix-missing-prototype-warning Fix duk_error_raw() warning with -Wmissing-prototypes	8 years ago
Sami Vaarala	eef2678280	Releases: duk_error_raw() -Wmissing-prototypes	8 years ago
Sami Vaarala	be480a5ae9	Add -Wmissing-prototypes Gives warnings when a function is defined before a declaration -- even when no calls happen before the definition/declaration. This is technically fine but maybe best avoided.	8 years ago
Sami Vaarala	ef5d8af90e	Example fixes for -Wmissing-prototypes	8 years ago
Sami Vaarala	6b1c78930b	Define duk_error_raw() without variadic macros too duk_error_raw() is used in internals (in one place) to allow an error throw to be omitted from the stack trace.	8 years ago
Brett Vickers	9e2f4a1d9a	Simplify calculation in duk_bi_date_get_local_tzoffset_windows_no_dst The previous version was using the current time, but that's unnecessary when daylight saving time isn't being taken into account.	8 years ago
Sami Vaarala	96d5677c63	Merge pull request #1387 from svaarala/durango-trivia Durango portability trivia	8 years ago
Sami Vaarala	343583d3a6	Releases: Durango portability improvements	8 years ago
Sami Vaarala	941e5755d4	Comment trivia	8 years ago
Sami Vaarala	3c491a63a3	More descriptive platform name for Durango	8 years ago
Sami Vaarala	02ab98361c	Merge pull request #1386 from arenanet/add-durango-platform Add the Durango platform.	8 years ago
Brett Vickers	6bf983567e	Add the Durango platform. The Durango platform is used by the Xbox One. This platform currently differs from the Windows platform only in that it does not support the SystemTimeToTzSpecificLocalTime API.	8 years ago
Sami Vaarala	f68d6332b5	Releases: module-duktape _snprintf()	8 years ago
Sami Vaarala	22966b96dd	Use _snprintf() prior to MSVC 2015	8 years ago
Sami Vaarala	a2c80b7992	Merge pull request #1383 from svaarala/runtest-massif-parsing-etc Runtest.py massif/memcheck parsing support	8 years ago
Sami Vaarala	2f97e4ebda	Runtest.py massif/memcheck parsing support	8 years ago
Sami Vaarala	42e00d89ec	Merge pull request #1312 from svaarala/symbol-check-unlikely Make symbol checks unlikely	8 years ago
Sami Vaarala	f0b07107fd	Releases: symbol likely/unlikely	8 years ago
Sami Vaarala	a08c85753e	Make symbol checks unlikely Usually symbol checks are in code paths expecting a string; make these unlikely. For code paths where a symbol is expected, make the check likely.	8 years ago
Sami Vaarala	a6a58a49c2	Merge pull request #1372 from svaarala/add-explicit-curr-act-pointer Add explicit current activation pointer	8 years ago
Sami Vaarala	1720ce3ba8	Releases: explicit thr->callstack_curr	8 years ago
Sami Vaarala	e472b6d4d2	Add thr->callstack_curr Makes common idiom of act = thr->callstack + thr->callstack_top - 1 shorter, footprint impact is about -0.5kB.	8 years ago

1 2 3 4 5 ...

8078 Commits (4380b9a80b790462a0d22a0eb07bed03f90c1abb) All Branches Search

8078 Commits (4380b9a80b790462a0d22a0eb07bed03f90c1abb)

All Branches