search for: chained_origin_with_signals

I'm compiling compiler-rt via CMake+Ninja on x86_64+ArchLinux and one of the tests fails on ToT: MemorySanitizer :: chained_origin_with_signals.cc The text expects uninitialized warnings while the execution prints nothing, thus FileCheck fails. Anyone seeing this? cheers, --renato

Hi Evgeniy, Yes, it is. The problem here is that the program doesn't fail on my box (release and debug builds), so I have no idea how to debug the problem. According to the test, it's ran as "not chained_origin_with_signals.cc.tmp", expecting it to fail. Also, the FileCheck expects to find warnings on the output, for which there is none Maybe I'm missing some CMake flag or library, and that's why the signal functionality is not working on my box? cheers, --renato On 25 July 2014 09:39, Evgeniy Stepanov...

...enato.golin at linaro.org> wrote: >> Hi Evgeniy, >> >> Yes, it is. The problem here is that the program doesn't fail on my >> box (release and debug builds), so I have no idea how to debug the >> problem. According to the test, it's ran as "not >> chained_origin_with_signals.cc.tmp", expecting it to fail. Also, the >> FileCheck expects to find warnings on the output, for which there is >> none >> >> Maybe I'm missing some CMake flag or library, and that's why the >> signal functionality is not working on my box? >> >&...

Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom