[Bug c++/54155] Newly compiled GCC 4.4.4 on Solaris sparc gives problem with -m32/-m64 flags

["ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54155

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
                 CC|                            |ro at gcc dot gnu.org

--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-08-02 15:17:25 UTC ---
> Without -m32: 
> COLLECT_GCC_OPTIONS='-o' 'test' '-v' '-shared-libgcc' '-mcpu=v9'
> With -m32: COLLECT_GCC_OPTIONS='-o' 'test' '-m32' '-v' '-shared-libgcc'
> '-mcpu=v9'
> 
> Without -m32: collect2 -V -Y P,/usr/ccs/lib:/usr/lib -rpath-link...
> With -m32: collect2 -V -m elf32_sparc -Y P,/usr/ccs/lib:/usr/lib -rpath-link
> ################################################################################
> Note: On another machine where the output of ld -V is as follows, gcc 4.4.4 is
> able to compile successfully with the -m32/-m64 options
> bash-3.00# /usr/local/bin/ld -V
> GNU ld (GNU Binutils) 2.20.1.20100303
>   Supported emulations:
>    elf32_sparc
>    elf64_sparc
> bash-3.00#
> ################################################################################
> If I replace only the ld from GNU Binutils 2.21.x with the ld from 2.20.x then
> the compilation is successful with -m32/-m64.
> Is this a bug in the GNU ld 2.21.x?

Certainly there is a mismatch between the compiler and the linker, and the
linker now rejecting elf32_sparc is unexpected.

Rainer, is that a known issue?