search for: alloca_vla_interact

(Resending with the correct mailing list address.) Hi, Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for powerpc64. I've had a look at why it doesn't work. I think the only problem is in the call to __asan_allocas_unpoison that is inserted at the end of the "for" loop (just before a stackrestore instruction). The call function is created something like this (paraph...

...and Yuri, as I think this is their code. > > On Thu, Nov 12, 2015 at 3:02 AM, Jay Foad <jay.foad at gmail.com > <mailto:jay.foad at gmail.com>> wrote: > > (Resending with the correct mailing list address.) > > Hi, > > Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for > powerpc64. I've had a look at why it doesn't work. I think the only > problem is in the call to __asan_allocas_unpoison that is inserted at > the end of the "for" loop (just before a stackrestore instruction). > > The call functio...

Jay, do you have a PowerPC64 target? If so, could you please check attached patch on PPC box? This is a draft patch, but it would be nice to make sure that we are moving to right direction here. Thanks, -Maxim On 18/11/15 00:12, Jay Foad wrote: >>> Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for >>> powerpc64. I've had a look at why it doesn't work. I think the only >>> problem is in the call to __asan_allocas_unpoison that is inserted at >>> the end of the "for" loop (just before a stackrestore instruction). &gt...

...; attached patch on PPC box? This is a draft patch, but it would be nice to >> make sure that we are moving to right direction here. >> >> Thanks, >> -Maxim >> >> >> On 18/11/15 00:12, Jay Foad wrote: >> >>> Currently test/asan/TestCases/alloca_vla_interact.cc is XFAILed for >>>>> powerpc64. I've had a look at why it doesn't work. I think the >>>>> only >>>>> problem is in the call to __asan_allocas_unpoison that is >>>>> inserted at >>>>> the end of the...

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...tial.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/alloca_overflow_right.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/alloca_safe_access.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/alloca_underflow_left.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/alloca_vla_interact.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/allocator_returns_null.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/asan_and_llvm_coverage_test.cc AddressSanitizer-i386-freebsd-dynamic :: TestCases/asan_options-help.cc AddressSanitizer-i386-freebsd-dynamic :: TestCase...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>