[ACTIVITY] 27 June - 1 July 2016
== 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 fix a few things * List of active environments with llvm-env [TCWG-640] [1/10] - Committed internally * Refactor SelectionDAGBuilder::visitInlineAsm [TCWG-643] [1/10] - In progress (trying to break it up into a few helper functions) * PR26038 - inline assembly assertion building ARM linux kernel [TCWG-590] [1/10] - Started investigating == Plan == * Address any review comments for TCWG-623 and TCWG-669 * Submit patches for TCWG-643 and TCWG-590 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 27 June - 1 July 2016
== 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 interworking thunks, should just be grunt-work to get done. Updated lld slides on llvm sprint presentation. == Plan == TCWG-653 and TCWG-612. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Asan output not symbolized
>> 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. >> >> Why am I lacking symbolization, and how do I achieve it? > > Are these full backtraces you got from ASan? If so, do you use stripped > libraries on your system (on Ubuntu, I guess, you do). Could this issue > (https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00132.html) be related to to > your problem? > Not stripped; they are [supposed to be] fully symbolized. Here's the CXXFLAGS used. Link occurs using $CXX with CXXFLAGS. $ cat asan-output.txt $ export CXXFLAGS="-DDEBUG -g3 -O0 -std=c++03 -mfpu=neon -fPIC -fsanitize=address -fno-omit-frame-pointer -D_GLIBCXX_DEBUG" ... We use one directory for *.h and *.cpp files. In addition, *.o files go in the same directory. We do it to avoid problems with debuggers finding symbols (it minimizes user questions). Here's the full output, if interested: http://pastebin.com/Zn4ADDQ6. It looks like there's some unbounded recursion going on, too. Let me look into the bug, thanks. Jeff ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Asan output not symbolized
>> >> 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 pc >> 0x38cbc5 bp 0xbea679e0 sp 0xbea679e4 >> >> AddressSanitizer: stack-buffer-overflow on address 0xbef0fe9c at pc >> 0x66117 bp 0xbef0fe68 sp 0xbef0fe6c >> > > Are these full backtraces you got from ASan? If so, do you use stripped > libraries on your system (on Ubuntu, I guess, you do). Could this issue > (https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00132.html) be related to to > your problem? I don't believe the bug report applies... Here's a crummy work around. First, install Clang on a machine, the do a `which asan_symbolize` if you get lucky, it will be there (I found one on my LeMaker HiKey). SCP it to the machine. Then: cubietruck:cryptopp$ ./cryptest.exe v 2>&1 | sed 's|/home/jwalton/cryptopp/||g' | asan_symbolize Using seed: 1467414010 Testing Settings... passed: Your machine is little endian. passed: Your machine allows unaligned data access. passed: sizeof(byte) == 1 passed: sizeof(word16) == 2 passed: sizeof(word32) == 4 passed: sizeof(word64) == 8 passed: sizeof(hword) == 2, sizeof(word) == 4, sizeof(dword) == 8 passed: hasNEON == 1, hasCRC32 == 0, hasAES == 0, hasSHA1 == 0, hasSHA2 == 0 = ==3719== ERROR: AddressSanitizer: stack-buffer-overflow on address 0xbebb9ac8 at pc 0x38b99d bp 0xbebb9990 sp 0xbebb9994 WRITE of size 4 at 0xbebb9ac8 thread T0 #0 0x38b99b in _ZN8CryptoPP6FilterC2EPNS_22BufferedTransformationE /home/jwalton/cryptopp/filters.cpp:27 #1 0x38b99b in _ZN8CryptoPP6FilterC2EPNS_22BufferedTransformationE /home/jwalton/cryptopp/filters.cpp:27 ... I could further pipe it through c++filt, but I have an idea of what to look for. Jeff ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
