>> 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 2
Thanks Jonathan,
>> If V9 is indeed required, is there a way to build without those libs? Or
>> has pre V9 support been dropped at some point?
>
> --disable-libitm --disable-libatomic
Ok, so those two switches will be required for non-v9 SPARC targets.
I still think this should be taken care of
Hi Eric
>> Removing "-mcpu=v9" allows the build to finalize.
>
> IIRC both libraries require the V9 architecture to work
> properly/efficiently.
I have successfully built without the switch, but I am not sure of the
effects at runtime.
If V9 is indeed required, is there a way to build without th
Hi all,
I have seen this in 4.8.2 but seems to be present since 4.7.0 (was added
by revision 184177 in libitm/configure.tgt):
# Map the target cpu to an ARCH sub-directory. At the same time,
# work out any special compilation flags as necessary.
case "${target_cpu}" in
...
sparc)
