Re: segmentation fault in t-toom53 test with MAC OS X Catalina (Clang 11.0)

2019-11-08 Thread JRR
There, tfib2m segfaults. Am 08.11.19 um 23:40 schrieb Marc Glisse: On Fri, 8 Nov 2019, JRR wrote: Interestingly now I get a segmentation fault in t-powm test. This is with a new Macbook Pro with i9. Are there any updates on this? If you want to test something, a recent snapshot from https

Re: segmentation fault in t-toom53 test with MAC OS X Catalina (Clang 11.0)

2019-11-08 Thread JRR
: One might take down MacPorts GCC on MacOS 10.14 and then update to MacOS 10.15, but then it cannot be updated unless MacPorts has done so. On 9 Oct 2019, at 00:52, JRR wrote: I see, I haven't updated my newer Macbook Pro from 2015 (which is Haswell) to 10.15, but updated the XCode

Re: segmentation fault in t-toom53 test with MAC OS X Catalina (Clang 11.0)

2019-11-09 Thread JRR
There are more problems in mpfr, and mpc does not even compile. Is this already known? Am 08.11.19 um 23:40 schrieb Marc Glisse: On Fri, 8 Nov 2019, JRR wrote: Interestingly now I get a segmentation fault in t-powm test. This is with a new Macbook Pro with i9. Are there any updates

Re: segmentation fault in t-toom53 test with MAC OS X Catalina (Clang 11.0)

2019-11-09 Thread JRR
Is it known: does the Security Integrity Protocol of macOS have any influence on this? Am 08.11.19 um 23:40 schrieb Marc Glisse: On Fri, 8 Nov 2019, JRR wrote: Interestingly now I get a segmentation fault in t-powm test. This is with a new Macbook Pro with i9. Are there any updates

Re: segmentation fault in t-toom53 test with MAC OS X Catalina (Clang 11.0)

2019-10-09 Thread JRR
I see, I haven't updated my newer Macbook Pro from 2015 (which is Haswell) to 10.15, but updated the XCode. There compilation and running the tests do work. Am 09.10.19 um 00:44 schrieb Hans Åberg: On 8 Oct 2019, at 23:59, Torbjörn Granlund wrote: Juergen Reuter writes: Please let me