https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69042
--- Comment #13 from amker at gcc dot gnu.org --- Simple summary. The test case provided in this PR is resolved by the two patches, but the problem still exists if the first function in compilation unit triggers the issue. This is because x86's inconsistent behavior of PIC_OFF_REG, discussed at https://gcc.gnu.org/ml/gcc/2016-02/msg00040.html Maybe this will be addressed in next stage 1. If we go deeper in IVOPT, we may be able to model that symbol PIC offset requires an additional register for m32. But this will be a target dependent issue, for example x86_64 may not have this issue. We then need a backend hook to get this information. But register pressure computation is far from a fine grain model anyway...
