This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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

--- Comment #7 from damz <dshanke at gmail dot com> 2012-08-08 17:40:37 UTC ---
(In reply to comment #5)
> > --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-08-02 15:17:25 UTC ---
> 
> >> 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.
> 
> Replacing the linker (or assembler) used at gcc configure time with a
> different one at runtime is not supported: the configure process
> determines several linker features and hardcodes the result into the
> compiler built.
> 
> >> Is this a bug in the GNU ld 2.21.x?
> 
> No, but gcc 4.4.4 doesn't support gld 2.21.  That version introduced the
> elf*_sparc_sol2 linker emulations, and this is only handled by gcc 4.4.5
> and newer.  Please note that both gcc 4.4 and 4.5 are ancient history by
> now and not supported any longer.
> 
> > 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?
> 
> In a way, yes, see above.
> 
>     Rainer

Thanks so much for the clarification! :)
How I wish that the supportability matrix was published.
Did I miss to see a document saying that ld 2.21 will not be supported by GCC
4.4.4 and below? :(
I was hoping that backward compatibility was mostly retained!


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]