hxcpp
hxcpp copied to clipboard
HaxeFoundation
Runtime files for c++ backend for haxe
Tested all kinds of variants (debug/release, 32bit/64bit) on Android and Switch and my example from earlier (attached it again for convenience) quickly crashes in MarkAlloc in all of them. Only...
The api.haxe.org doc generation failed with seg fault with hxcpp 4.0.64. https://travis-ci.org/HaxeFoundation/api.haxe.org/builds/608451154#L846 I've just pinned hxcpp version to 4.0.52 and CI worked as expected now.
Since https://github.com/HaxeFoundation/haxe/commit/6b7db0254e0035a2380b985fee1ff1160fd23ef2 `Array.iterator()` should return an instance of `haxe.iterators.ArrayIterator`. Currently this happens: ```haxe trace(([1, 2, 3]:Iterable).iterator()); // Object var it:ArrayIterator = cast ([1, 2, 3]:Iterable).iterator(); trace(it); // null ```
[test.zip](https://github.com/HaxeFoundation/hxcpp/files/3655453/test.zip) run in hxcpp got nothing error information but crash. but Hashlink target run well. @hughsando
Added x86_64 support in the GCC toolchain for older NDKs - I tested with NDK15c, but should be compatible with 14b as well.
I'm compiling Win32 builds with MSVS 2013 express. I had to disable unicode strings, because changing compiler is not possible for me at the moment and latest hxcpp runtime requires...
It looks like `THREAD_TERMINATED` events can report a `threadNumber` of -1 in some situations. See https://github.com/vshaxe/hxcpp-debugger/issues/22 for the full details and a repro case.
Since a long time I experience a very rare startup crash in GCFreeZone (see also my confusion in #758). When it happens, it only happens rarely, preferably in release builds...
On windows 64 bit I have random issue when some sockets become not valid. Error 10038. I didn't see this on Win 32 or other platforms yet. It's good to...