Re: [PATCH 4/9] Expose forcibly_ggc_collect and run it after all selftests

2016-09-16 Thread Jeff Law
On 09/08/2016 06:30 PM, David Malcolm wrote: Force a GC at the end of the selftests, to shake out GC-related issues. For example, if any GC-managed items have buggy (or missing) finalizers, this last collection will ensure that things that were failed to be finalized can be detected by valgrind.

[PATCH 4/9] Expose forcibly_ggc_collect and run it after all selftests

2016-09-08 Thread David Malcolm
Force a GC at the end of the selftests, to shake out GC-related issues. For example, if any GC-managed items have buggy (or missing) finalizers, this last collection will ensure that things that were failed to be finalized can be detected by valgrind. gcc/ChangeLog: * ggc-tests.c (forcibl