Ivan Maidanski comments

Results 817 comments of


                                            Ivan Maidanski

Unexpected termination of gctest on Cygwin64 if incremental mode and thread-local-alloc are on

Latest master (a8c5ee41a) 64-bit build fail: https://ci.appveyor.com/project/ivmai/bdwgc/builds/24025740/job/lp8rn2ythx3escyb

Unexpected termination of gctest on Cygwin64 if incremental mode and thread-local-alloc are on

For an unknown reason, GC_write_fault_handler is called only once.

Unexpected termination of gctest on Cygwin64 if incremental mode and thread-local-alloc are on

The current workaround is d040adef5 (to disable MPROTECT_VDB on Cygwin)

gctest hangs on NetBSD

Please provided stack trace of all threads.

Specify default values in README environment

Sure. If you could propose a patch it would be great!

Specify default values in README environment

Same applies to README.macros.

Specify default values in README environment

BTW. Out of scope of this issue, but further it would be nice to convert README.environment and README.macros to markdown format (e.g. environment.md and macros.md)

Support incremental collection on E2K

Commit c5c7c5324 supports mprotect-based VDB but only if no THREAD_LOCAL_ALLOC. Note about SOFT_VDB: soft dirty bit is not supported by Linux kernel on e2k.

Support incremental collection on E2K

About SIGILL (why -O0 or -fsemi-spec-ld is needed): http://ftp.altlinux.com/pub/people/mike/elbrus/docs/elbrus_prog/html/chapter2.html

Support incremental collection on E2K

It could be easily reproduced on master (commit 308aafa40) with the following command: ./autogen.sh && ./configure && make check CFLAGS_EXTRA="-D MPROTECT_VDB" Repeat ./gctest several times. (Rate: ~1/4)