https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102115
jcmvbkbc at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcmvbkbc at gcc dot gnu.org Last reconfirmed| |2021-09-07 Assignee|unassigned at gcc dot gnu.org |jcmvbkbc at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from jcmvbkbc at gcc dot gnu.org --- Thanks for the report and analysis. The following part needs a bit of explanation: After the 64a54505ec8249178b9767d1420354f8eb55de50, using -Os on x86_64-w64-mingw32 *may* result in missing function symbol in the example test.ii attached if the symbol's address can be compressed into small number accepted by the movi + slli. It's not about the address that corresponds to the symbol in the target code (e.g. in the attached example the target addresses are all unknown), but about the RTX node address that describes the symbol inside the compiler. That makes this bug hard to reproduce.