https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95285
--- Comment #3 from Bu Le <bule1 at huawei dot com> --- (In reply to Wilco from comment #2) > Is the main usage scenario huge arrays? If so, these could easily be > allocated via malloc at startup rather than using bss. It means an extra > indirection in some cases (to load the pointer), but it should be much more > efficient than using a large code model with all the overheads. Thanks for the reply. The large array is just used to construct the test case. It is not a neccessary condition for this scenario. The common scenario is that the symbol is too far away for small code model to reach it, which cloud also result from large amount of small arrays, structures, etc. Meanwhile, the large code model is able to reach the symbol but can not be position independent, which cause the problem. Besides, the code in CESM is quiet complicated to reconstruct with malloc, which is also not an acceptable option for my customer. Clear enough for your concern?
