[Bug ld/17219] ld/mips: can no longer build libstdc++ (gcc 4.8/4.9)

[matthew.fortune at imgtec dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=17219

Matthew Fortune <matthew.fortune at imgtec dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at sourceware dot org   |matthew.fortune at 
imgtec dot com

--- Comment #4 from Matthew Fortune <matthew.fortune at imgtec dot com> ---
(In reply to Aaro Koskinen from comment #3)
> I get similar errors with release 2.25 binutils. Trying to cross-build MIPS
> GCC configured with --with-float=soft fails miserably. With hard float there
> is no issues (or binutils 2.24 with soft float). Apparently 2.25 binutils
> require some additional flags which GCC 4.9 fails to pass?
> 
> Is there any simple workaround for this?

This is a compiler driver issue. The LD failures relating to relocations are
somewhat strange but I believe they are not the important part here. The ABI
problems from the assembler warnings are the root cause.

I've put together a backport of minimal GCC driver changes for the GCC 4.9
branch and that is pretty much the only way to resolve this. The new
floating-point ABI checks in the assembler unfortunately couldn't be seamless
for everything and soft-float is the case that takes most of the pain.

With the GCC patch in place I managed to build a GCC 4.9 (branch) + binutils
2.25 (branch) soft-float toolchain. I'll post the patch to GCC at some point
tomorrow and try to remember and update this ticket with a link. The patch
should apply cleanly to any GCC 4.9 release so will have to be ported by a
distribution maintainer if anyone wants any of the already released GCC 4.9.x
compilers alongside binutils 2.25 onwards.

I will look at a similar patch for GCC 4.8 if there is sufficient call for that
alongside binutils 2.25.

Sorry for not getting to the GCC 4.9 patch sooner, I knew about it and never
quite got to doing it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.