Launchpad has imported 3 comments from the remote bug at https://llvm.org/bugs/show_bug.cgi?id=27836.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2016-05-23T01:56:34+00:00 Geunsik Lim wrote: Created attachment 16399 ARM: don't attempt to merge litpools referencing different PC-anchors. There are four thread local storage (TLS) models in Clang/LLVM as following: 1) global-dynamic TLS model 2) local-dynamic TLS model 3) local-exec TLS model 4) initial-exec TLS model and emulated-TLS (for Android S/W platform)?? Even though, We can build run normally with the static relocation method by selecting the initial-exec TLS model instead of global-dynamic TLS model (by default) , We need to run the clang application code with global-dynamic (or local-dynamic) TLS model in order that we support some applications is working with dlopen(3) library call. We have found the appropriate solution for some clang/LLVM applications including 1) __thread variables and 2) -O2/-O3 of the clang language. Could you apply this patch to Ubuntu 14.04 LTS and Ubuntu 16.04 LTS repository? * LLVM: Revision 268662 (ARM: don't attempt to merge litpools referencing different PC-anchors.) http://llvm.org/viewvc/llvm-project?view=revision&revision=268662 Below is the mailing list discussed to fix this issue. http://lists.llvm.org/pipermail/llvm-dev/2016-May/098974.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160502/353476.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160509/355091.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160516/356679.html * Before r268662: ubuntu@raspberrypi2#> ./corerun ./hello.exe (with -O2/-O3) Segmentation Fault * After r268662: ubuntu@raspberrypi2#> ./corerun ./hello.exe (with -O2/-O3) Hello!!! Welcome to .NET Core (CoreCLR) world.!!! Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- defaults/+bug/1584089/comments/5 ------------------------------------------------------------------------ On 2016-05-23T02:00:19+00:00 Geunsik Lim wrote: We have posted this issue and patch to Ubuntu's launchpad bug system (e.g. llvm-defaults package) as following: * https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1584089 Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- defaults/+bug/1584089/comments/6 ------------------------------------------------------------------------ On 2016-05-24T20:23:00+00:00 Tim Northover wrote: As noted, this was fixed by r268662. Reply at: https://bugs.launchpad.net/ubuntu/+source/llvm- defaults/+bug/1584089/comments/9 ** Changed in: llvm Status: Unknown => Fix Released ** Changed in: llvm Importance: Unknown => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu. https://bugs.launchpad.net/bugs/1584089 Title: Segfault of __thread varaible in Linux/ARM due to bug of LLVM ARM code generation Status in LLVM: Fix Released Status in llvm package in Ubuntu: Confirmed Status in llvm-defaults package in Ubuntu: Confirmed Status in llvm-toolchain-3.6 package in Ubuntu: Confirmed Bug description: There are four thread local storage (TLS) models in Clang/LLVM as following: 1) global-dynamic TLS model 2) local-dynamic TLS model 3) local-exec TLS model 4) initial-exec TLS model and emulated-TLS (for Android S/W platform)?? Even though, We can build run normally with the static relocation method by selecting the initial-exec TLS model instead of global- dynamic TLS model (by default) , We need to run the clang application code with global-dynamic (or local-dynamic) TLS model in order that we support some applications is working with dlopen(3) library call. We have found the appropriate solution for some clang/LLVM applications including 1) __thread variables and 2) -O2/-O3 of the clang language. Could you apply this patch to Ubuntu 14.04 LTS and Ubuntu 16.04 LTS repository? * LLVM: Revision 268662 (ARM: don't attempt to merge litpools referencing different PC-anchors.) http://llvm.org/viewvc/llvm-project?view=revision&revision=268662 https://llvm.org/bugs/show_bug.cgi?id=27836 Below is the mailing list discussed to fix this issue. http://lists.llvm.org/pipermail/llvm-dev/2016-May/098974.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160502/353476.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160509/355091.html http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20160516/356679.html * Before r268662: ubuntu@raspberrypi2#> ./corerun ./hello.exe (with -O2/-O3) Segmentation Fault * After r268662: ubuntu@raspberrypi2#> ./corerun ./hello.exe (with -O2/-O3) Hello!!! Welcome to .NET Core (CoreCLR) world.!!! To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1584089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
