http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47119
--- Comment #3 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2010-12-31 20:35:15 UTC --- (In reply to comment #2) > I objected to a previous patch version using the weak attribute and > thought that a way was found at that point to do without it. There's no > way it should be needed on the host for anything reasonable in GCC I'm not saying that this is doing something reasonable - I just wanted to know how much else it takes to get "make all-gcc" with --enable-werror-always to succeed. >- I > don't know what this port is trying to do but there's bound to be a better > way. Split up objects as necessary and ensure that exactly one > implementation of each function needed is linked into each compiler. If > the problem is generic functions calling C-family ones, use function > pointers initialized at an appropriate point. (REGISTER_TARGET_PRAGMAS is > abused by ARM as a "C family initialization hook" though a separate hook > would be better.) C and C++ frontends each have their own, different versions of these functions, but then these functions area also wanted for linking the ada, lto, and go compilers, and for collect2. So one uniform "C family initialization hook" would not be enough. Unless someone can re-unify the different implementations for the C language family. Maybe this will need some more language hooks. But would that be effort well spent? I.e. does anyone care about this port?
