o One day off (2/10)
== Progress ==
o Extended Validation (3/10)
- Benchmarking job babysitting.
- Looked at Dejagnu issue (pid killing, resurrected an old patch)
o Upstream GCC (3/10)
- __sync bultin fix for ARMv8.1:
Careful read of the doc shows that there is no issue with the
== Progress ==
* Validation
- reviews/cleanup in Jenkins jobs
- experimented with Xenial and docker builders
* GCC
- PR 67591 (ARM v8 Thumb IT blocks deprecated)
- neon-fp16 tests consistency patch committed
- a couple of regressions flagged on trunk
* misc (conf-calls, meetings, emai
# Progress #
* TCWG-655, Workaround ARM linux kernel ptrace bug on setting VFP
registers. [2/10]
Think about different approaches to workaround the kernel bug, but
can't work unfortunately. Propose an approach that workaround it in
gdb testing by setting affinity if the kernel is known
On 02/07/2016 05:29, Jeffrey Walton wrote:
> On Sun, Jun 26, 2016 at 10:33 PM, Jeffrey Walton wrote:
>> Hi Everyone,
>>
>> I have a test script from help that repeatedly builds and runs a
>> library under different configurations. The script includes multiple
>> Asan tests.
>>
>> The Asan tests
>> Mystery solved... GCC 4.8 does not provide a symbolizer.
>>
>> From a new comment on the GCC bug report
>> (https://bugzilla.redhat.com/show_bug.cgi?id=1250844#c6):
>
> Even with symbolizer you may face some issue with ASAN on ARM.
> Check this llvm bug report [1].
>
> [1] https://llvm.org/bugs/
On 04/07/2016 15:56, Jeffrey Walton wrote:
>>> Mystery solved... GCC 4.8 does not provide a symbolizer.
>>>
>>> From a new comment on the GCC bug report
>>> (https://bugzilla.redhat.com/show_bug.cgi?id=1250844#c6):
>>
>> Even with symbolizer you may face some issue with ASAN on ARM.
>> Check this
