Jack Howarth writes:
Torbjörn,
Are you just using...
./configure
Yes.
or are you explicitly passing -fstack-check to clang on CFLAGS and
CXXFLAGS? I did notice one extra oddity to this bug. When the default stack
checking in Xcode 11 clang is used, the t-powm test case
On Sat, 9 Nov 2019, JRR wrote:
There are more problems in mpfr, and mpc does not even compile.
If MPC does not compile, I think you are on the wrong list to report it...
--
Marc Glisse
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
Dear Juergen,
> There are more problems in mpfr, and mpc does not even compile.
> Is this already known?
please report mpfr and mpc specific issues to the corresponding lists.
Paul Zimmermann
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
On Fri, Nov 8, 2019 at 5:53 PM Torbjörn Granlund wrote:
> Jack Howarth writes:
>
>Torbjörn,
> Are you using the clang from Xcode 11?
>
> Yes, of course.
>
> --
> Torbjörn
> Please encrypt, key id 0xC8601622
>
Torbjörn,
Are you just using...
./configure
or are you
How do we proceed? All other tests work fine.
The architecture is broadwell, clang is
Apple clang version 11.0.0 (clang-1100.0.33.12)
Target: x86_64-apple-darwin19.0.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
There
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 on this?
