[ACTIVITY] 27 June - 1 July 2016

2016-07-01 Thread Diana Picus
== Progress == * ARM: Do not test for CPUs, use SubtargetFeatures [TCWG-623] [4/10] - Committed another patch upstream, 3 more in review * ARM: Different ABI functions based on optimization level [TCWG-669] [3/10] - Make sure we're ABI-compliant at -O0 - Patch in upstream review, need to fi

[ACTIVITY] 27 June - 1 July 2016

2016-07-01 Thread Peter Smith
== Progress == TCWG-653 ARM/Thumb interworking veneers Have completed an implementation, now in upstream review. Had initial set of comments and posted an update. Likely to take several iterations before commit TCWG-612 ARM TLS support in LLD Made a start. Looks to be more straightforward the i

Re: Asan output not symbolized

2016-07-01 Thread Jeffrey Walton
>> The test program is always built with at least -g2, and sometimes >> built with -g3. However, I am not seeing the symbolication. According >> to the GCC folks, asan_symbolize is not required for GCC because it >> uses libbacktrace. Also see >> http://bugzilla.redhat.com/show_bug.cgi?id=1250844.

Re: Asan output not symbolized

2016-07-01 Thread Jeffrey Walton
>> >> AddressSanitizer: stack-buffer-overflow on address 0xbec57b18 at pc >> 0x38c651 bp 0xbec579e0 sp 0xbec579e4 >> >> AddressSanitizer: stack-buffer-overflow on address 0xbedbae9c at pc >> 0x6553f bp 0xbedbae68 sp 0xbedbae6c >> >> AddressSanitizer: stack-buffer-overflow on address 0xbea67b18 at p