How to prune tests that are too large for a tiny memory model in libstdc++?

2014-11-28 Thread Kyrill Tkachov

Hi all,

I'm seeing some relocation truncation failures in the libstdc++ 
testsuite where the test
is too large to fit into the memory model. In the gcc testsuite we mark 
these tests as unsupported

using something like the below fragment in gcc-dg.exp

if { [regexp "(^|\n)\[^\n\]*: relocation truncated to fit" $text]
  && [check_effective_target_tiny] } {
return "::unsupported::memory full"
}

Where would I go about adding similar logic in the libstdc++ tesuite 
.exp files?

I can't find similar pruning infrastructure there...

Thanks,
Kyrill



Re: Testing Leak Sanitizer?

2014-11-28 Thread Renato Golin
On 27 November 2014 at 21:48, Christophe Lyon
 wrote:
> On 30 September 2014 at 19:08, Konstantin Serebryany
>  wrote:
>> Correct, you can run tests from llvm tree with any compiler.
>> https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerTestSuite
>>
>
> I've read that document, and as a first step I wanted to build LLVM +
> run the tests in the "best case" (before any modifications I could
> make, and to have a reference to compare with GCC).
> I have a few questions.
>
> To have clang as the "toolchain I want to test", I added the clang
> sources under llvm_tmp_src/tools,  and compiler-rt sources under
> projects.
>
> I managed to run the tests, but I couldn't find the detailed logs.
> I added -DLLVM_LIT_ARGS=-v when calling cmake, which gave me a list like:
> XFAIL: AddressSanitizer64 :: TestCases/use-after-scope.cc (245 of  249)
> PASS: AddressSanitizer64 :: TestCases/use-after-poison.cc (246 of 249)
>
> 1- I suppose there are more details, like gcc.log. Where are they?
> 2- this is running x86_64 native tests, how can I cross-test with
> aarch64 (using qemu for instance)?

Hi Cristophe,

I'm adding Greg, since he made it work a while ago. I remember he
added a few options to CMake and LIT to run the tests on an emulator
(basically QEMU), but I'm not sure all the cases were covered and
everything was working.

Meanwhile, can you build that natively on AArch64? I remember I've ran
all compiler-rt tests on AArch64, including the sanitizers, last
March. The results were encouraging... :)

cheers,
--renato