Diff Detail
Event Timeline
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | Is there a reason you are not using the generic aarch64/linux mappings below? |
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | The Android mapping is different from Mapping39 in kLoAppMemBeg-kLoAppMemEnd. Because |
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | You mean PIE? I've added a comment to http://reviews.llvm.org/D14199. I don't mind going ahead with this one and figuring out if we want to unify the mappings later. |
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | Yes, I mean PIE. It might be related to kernel version, or architecture. I am not sure. |
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | As I commented on the aarch64-linux TSAN mapping unification discussion [1] I did check the tests with -fpic -pie build and I saw no issue. I checked on a recent kernel (3.19) and on this configuration the PIE addresses for TSAN builds are se on 0x7f.. range. I will check for 42-bits if TSAN tests fail with PIE build. |
lib/tsan/rtl/tsan_platform.h | ||
---|---|---|
129 | My first analysis was flawed and PIE flags was not really being used when building the binaries. I rechecked on both 39 and 42 bits VMA and indeed current mapping scheme for aarch64-linux does not support PIE configurations. I have created the revision [1] to fix this issue. I am not sure if this will work for aarch64-android. |
Is there a reason you are not using the generic aarch64/linux mappings below?
For ASan/aarch64/android, I've noticed that ART requires a first 4GB mapping, which seems incompatible with this layout.