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

2014-06-03 Thread Carlos Sánchez de La Lama
>> 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

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

2014-06-03 Thread Eric Botcazou
> V9 is currently bound to 64bit, you can't build a sparc-linux-gnu compiler > defaulting to V9 without patches. libitm was tested on SPARC/Linux though. -- Eric Botcazou

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

2014-06-03 Thread Matthias Klose
Am 02.06.2014 22:30, schrieb Eric Botcazou: >> I have successfully built without the switch, but I am not sure of the >> effects at runtime. > > For sure libitm cannot work, there is a 'flushw' in config/sparc/sjlj.S. > >> If V9 is indeed required, is there a way to build without those libs? Or >

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

2014-06-02 Thread Eric Botcazou
> I have successfully built without the switch, but I am not sure of the > effects at runtime. For sure libitm cannot work, there is a 'flushw' in config/sparc/sjlj.S. > If V9 is indeed required, is there a way to build without those libs? Or > has pre V9 support been dropped at some point? No,

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

2014-06-02 Thread Carlos Sánchez de La Lama
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

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

2014-06-02 Thread Jonathan Wakely
On 2 June 2014 12:38, Carlos Sánchez de La Lama wrote: > 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

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

2014-06-02 Thread Carlos Sánchez de La Lama
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

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

2014-06-02 Thread Eric Botcazou
> # 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) > case " ${CC} ${CFLAGS} " in > *" -m64 "*) > ;; > *) > if test -z "$w