Re: PPC64: fpsqrt instruction

Hi Bas, Thank you. Could you please upload the libm when you are finished with compiling? I would like to test it on my Cyrus board. Thanks, Christian On 06 February 2018 at 6:18PM, Bas Vermeulen wrote: Hi Christian, I am running into a similar problem with my T2080 (using an e6500). I'm

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

On 02/06/2018 07:22 PM, Bas Vermeulen wrote: > I just checked gcc's configure, and that doesn't take --with-cpu= as an > argument. It doesn't fail when it has it, but it doesn't actually do anything > with it > either. > So my patch would be the correct way to handle this. That's because you

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

I am evaluating the following patch to gcc-7 to fix the problem. It's currently building, I'll follow up when I know it works. The patch is added to debian/rules.patch to get it included. Bas Vermeulen On Tue, Feb 6, 2018 at 5:16 PM, Lennart Sorensen < lsore...@csclub.uwaterloo.ca> wrote: > On

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

On Tue, Feb 06, 2018 at 06:58:55PM +0100, John Paul Adrian Glaubitz wrote: > It would be nice if anyone who cares about the ppc64 could actually > post what kind of hardware they have. We should find a consensus on > where to put the baseline. Well at least the CPUs listed on

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

On 02/06/2018 06:03 PM, Bas Vermeulen wrote: > Mostly because I didn't know/think of that. But you are right, that would be > better. So, the file you want to modify is: > https://sources.debian.org/src/gcc-7/7.3.0-1/debian/rules2/#L380-L392 It would be nice if anyone who cares about the ppc64

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

I just checked gcc's configure, and that doesn't take --with-cpu= as an argument. It doesn't fail when it has it, but it doesn't actually do anything with it either. So my patch would be the correct way to handle this. Bas Vermeulen On Tue, Feb 6, 2018 at 6:58 PM, John Paul Adrian Glaubitz <

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

I get that. But configure in the gcc sources doesn't actually process those. So while they are in rules2, it doesn't actually change anything. See https://github.com/gcc-mirror/gcc/blob/da8dff89fa9398f04b107e388cb706517ced9505/configure and search for with-cpu (which would catch both

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

On 02/06/2018 07:29 PM, Bas Vermeulen wrote: > I get that. But configure in the gcc sources doesn't actually process those. > So while they are in rules2, it doesn't actually change anything. > > See  > https://github.com/gcc-mirror/gcc/blob/da8dff89fa9398f04b107e388cb706517ced9505/configure >

PPC64: fpsqrt instruction

Hi All, I use Debian Buster/Sid PPC64 on my Cyrus board with a P5020 SoC [1]. The E5500 fpu doesn't have a fpsqrt instruction. Does Debian's libm have support for emulation of the fpsqrt instruction? Thanks, Christian [1]

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

On Tue, Feb 06, 2018 at 03:40:20PM +0100, Bas Vermeulen wrote: > I am trying to run the ppc64 unstable on a Freescale T2080, which uses the > e6500 CPU. Running python (or any other application using sqrt or sqrtf) > will cause an illegal instruction exception, because the sqrtf opcode is > not

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

> On Feb 6, 2018, at 5:26 PM, Bas Vermeulen wrote: > > I am evaluating the following patch to gcc-7 to fix the problem. It's > currently building, I'll follow up when I know it works. The patch is added > to debian/rules.patch to get it included. Why do you want to patch

Re: PPC64: fpsqrt instruction

Hi Christian, I am running into a similar problem with my T2080 (using an e6500). I'm currently rebuilding gcc to build for powerpc64 by default, eliminating those from being generated by default. Once that is done, I'll have to rebuild glibc with the new gcc compiler to update libm. Bas

PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

Hi, I am trying to run the ppc64 unstable on a Freescale T2080, which uses the e6500 CPU. Running python (or any other application using sqrt or sqrtf) will cause an illegal instruction exception, because the sqrtf opcode is not supported on the e6500. This seems to be caused by gcc compiling

Re: PPC64: gcc currently compiles for power4 by default, causing glibc's sqrtf to fail on e6500

Mostly because I didn't know/think of that. But you are right, that would be better. Bas Vermeulen On Tue, Feb 6, 2018 at 5:48 PM, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> wrote: > > > On Feb 6, 2018, at 5:26 PM, Bas Vermeulen wrote: > > I am evaluating the