This is the mail archive of the
mailing list for the GCC project.
- From: Christophe Lyon <christophe dot lyon at linaro dot org>
- To: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 2 Jun 2014 17:25:19 +0200
- Subject: Cross-testing libsanitizer
- Authentication-results: sourceware.org; auth=none
I am updating my (small) patch to enable libsanitizer on AArch64, but
I am wondering about the testing.
Indeed, when testing on my laptop, execution tests fail because
libsanitizer wants to allocated 8GB of memory (I am using qemu as
When running on servers with more RAM, the tests pass.
I suspect this is going to be a problem, and I am wondering about the
best approach. When I enabled libsanitizer for ARM, I already had to
introduce check_effective_target_hw to avoid libsanitizer tests
involving threads because of qemu inability to handle them properly.
I could probably change this function into
check_effective_target_qemu, but that might not be acceptable (and it
would be used for 2 different purposes: threads and too much memory