Move GC to bdwgc #6
Conversation
|
Hey @chenyukang! Looks interesting. What's the difference between bdwgc and libgc? It seems to be coming from the same project. Is it just a more recent version? |
|
Hi @macournoyer , |
|
and bdwgc is depend on git://github.com/ivmai/libatomic_ops.git, |
|
I'm having trouble compiling on Mac OS X. Despite updating autoconf and such. Did you use clang or gcc? |
|
maybe you haven't install pkg-config? clang and gcc are both OK for me. |
|
Yes I got pkg-config and autoconf 2.69 like mentioned here: ivmai/bdwgc#16 |
|
the GC should just be removed from the source tree and the system-package-manager provided version used instead. boehm GC is a highly non-portable PoS (it invokes UB, installs signal handlers for segfaults, uses non-standard signals, tries to determine the start address of stack etc...) that needs a ton of fiddling around in its config.h to make it work on any slightly non-standard platform (i know this because i had to port it to my distro sabotage-linux, based on musl libc). |
boehm GC is a highly problematic package, since what it tries to achieve is not possible in standard C, so it must use all kinds of nasty platform-specific tricks to get start offset of stack and so on. for this reason, some or most distributions apply custom settings or even patches to make it work. these tweaks are not available when embedding the source of boehm into the tree and hoping that it will turn out to work well... windows users are advised to install the version provided by mingw package manager, while mac os users can use homebrew's version. closes #6 closes #9 closes #4
boehm GC is a highly problematic package, since what it tries to achieve is not possible in standard C, so it must use all kinds of nasty platform-specific tricks to get start offset of stack and so on. for this reason, some or most distributions apply custom settings or even patches to make it work. these tweaks are not available when embedding the source of boehm into the tree and hoping that it will turn out to work well... windows users are advised to install the version provided by mingw package manager, while mac os users can use homebrew's version. closes #6 closes #9 closes #4
boehm GC is a highly problematic package, since what it tries to achieve is not possible in standard C, so it must use all kinds of nasty platform-specific tricks to get start offset of stack and so on. for this reason, some or most distributions apply custom settings or even patches to make it work. these tweaks are not available when embedding the source of boehm into the tree and hoping that it will turn out to work well... windows users are advised to install the version provided by mingw package manager, while mac os users can use homebrew's version. closes #6 closes #9 closes #4
boehm GC is a highly problematic package, since what it tries to achieve is not possible in standard C, so it must use all kinds of nasty platform-specific tricks to get start offset of stack and so on. for this reason, some or most distributions apply custom settings or even patches to make it work. these tweaks are not available when embedding the source of boehm into the tree and hoping that it will turn out to work well... windows users are advised to install the version provided by mingw package manager, while mac os users can use homebrew's version. closes #6 closes #9 closes #4
Hi ,
I got segment fault in Mac OS X 10.8.4, and moving bdwgc fixed this.
also tested this on Linux .