Relocation Overflow Error about popcorn-compiler HOT 7 OPEN

I don't have a fix, but this is a known (but not documented until now) issue with some of the class C benchmarks.

We've previously dealt with it by simply ignoring class C for the problematic benchmarks. Obviously not sustainable in the long-term, of course.

from popcorn-compiler.

Could this be solved by changing the enormous amount of static data NPB is declaring (especially in Class C) to malloc?

from popcorn-compiler.

Yes, very probably. But we would like to avoid modifying the applications(?)

from popcorn-compiler.

I did it previously for IS, it was pretty easy. What is the reason behind not modifying the applications?

from popcorn-compiler.

AFAIK: Until known, one of the selling point of popcorn was that it "Bridges the Programmability Gap in Heterogeneous-ISA Platforms". Meaning that unmodified applications can run on heterogeneous platform.
If we start saying that <<we modified the applications to overcome this problem, although this problem has nothing to do with heterogeneity...>> It may delude our claim?

from popcorn-compiler.

No, in my opinion it is fine. It's your research so your choice in the end, but one might argue that changing this giant amount of static memory to dynamically allocated one is actually making NPB closer to a real application ...

from popcorn-compiler.

Update -- when digging into some TLS fixes I learned that LLVM uses R_AARCH64_TLSLE_ADD_TPREL_[HI12 | LO12] relocations for TLS addresses. These two relocations combine together to give a total addressable range from 0 - 2^24 (16 MB) from the TLS pointer. Because we're currently restricted to the initial-exec TLS model, there's not much we can do from the compiler side. So, if your application is using more than 16MB of TLS, it'll have to be changed to compile.

from popcorn-compiler.