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 #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-08-09 10:45:20 UTC ---
> --- Comment #7 from damz <dshanke at gmail dot com> 2012-08-08 17:40:37 UTC ---

> How I wish that the supportability matrix was published.

I hope you understand that this is completely unfeasible: I'm currently
testing gcc 4.6/4.7/4.8 on Solaris 8/9/10/11, both sparc and x86.
Adding older gcc releases (which are no longer maintained anyway) and
more than one (the current) binutils release to that testing simply
cannot be done in reasonable time, with finite amounts of diskspace, and
man power to analyse the results.

> Did I miss to see a document saying that ld 2.21 will not be supported by GCC
> 4.4.4 and below? :(

No, but in general (which is not yet true for gcc 4.4) I try to list the
latest binutils version known to work with that version of gcc.  With
newer binutils releases, you're on your own.  They may well work, but no
guarantees.

> I was hoping that backward compatibility was mostly retained!

Agreed, but as I said when I found that gcc 4.4 doesn't work with gld
2.21, I immediately backported the patch to that release branch.

    Rainer


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