https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108261
--- Comment #10 from Iain Sandoe <iains at gcc dot gnu.org> --- Initial questions (still digesting the remainder). -------- when a module has the same name but a different interface are the symbols distinct (i.e. mangled differently)? If not: - then I can see how it works with static archives - because the static linker picks the first one presented. - but multiple shared libraries in the same process, with the same symbol in them would seem to be challenging (I'm not sure how the various dynamic loaders would behave - i.e. the load order might not be sufficient?). If they are: - we could still build a monolithic library; it is up to the FE (presumably in conjunction with the include paths) to ensure that it references the symbol that is relevant to the interface style (iso/pim) chosen.
