http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47119
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-12-31 20:03:27 UTC --- On Fri, 31 Dec 2010, amylaar at gcc dot gnu.org wrote: > There are a lot more problems with this port. Here is a patch that makes > the port sort-of build when using GCC as the build compiler; it uses the > weak attribute to work around some issues with having different target > hooks depending on the input language. 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 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.)
