This is the mail archive of the 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]

Re: lib{atomic, itm}/configure.tgt uses -mcpu=v9 as default for sparc

>> IMHO an efficiency enhancement should not prevent running less
>> efficiently on a supported architecture. If target triple is
>> sparcv9-*-*, the next case will match and will add the "-mcpu=v9" to
>> XCFLAGS, but adding it for non-v9 sparc-*-* targets is at least weird.
> Well, V9 is about 20 years old now so defaulting to it is not unreasonable, 
> especially for all the native OSes.  But patches are of course
> welcome.

You might be right. My point was if target was not v9, configure should
take care of whatever is needed to build a working compiler (and target
libraries) without passing extra switches (probably setting UNSUPPORTED
in sparc-*-* cases of configure.tgt).

However, I have got the latest config.guess from git and now I see
sparc-*-* is not enough to ensure v7 or v8, but it is also a valid
triple for v9 targets, so there is no way to configure script to know if
it can use v9 or not, and just avoiding v9 optimizationes in all SPARC
compilers is clearly wrong. So I agree defaulting to v9 is correct.

I will build with the suggested disable switches. Thank you!


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