Re: GMP 6.1.2: 32-bit ARM build failure on 64-bit hardware with CFLAGS=-g

> On 24 Jan 2018, at 18:09, Torbjörn Granlund wrote: > > If you override flags for choosing the architecture level and/or ABI, > you cannot expect things to work. > > If so, is there another easy with debug info, without knowing in > advance what compiler flags configure

Re: repl-vsnprintf.c:396:0: error: ISO C forbids an empty translation unit

> On 13 Feb 2018, at 12:24, Torbjörn Granlund wrote: > > Dennis Clarke writes: > > As a minor annoyance it does cause gcc ( recent versions 7.x ) to fail. > Oddly enough ye Oracle Studio 12.6 cc running in strict c99 mode is fine > and happy with

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 8 Nov 2019, at 18:26, Marco Bodrato wrote: > > Il Ven, 8 Novembre 2019 4:59 pm, Niels Möller ha scritto: >> Hans Åberg writes: >> >>> How about memory allocations? — There is info here, suggesting >>> uninitialized memory access in the test su

Re: macOS Catalina: FAIL: t-powm

> On 15 Nov 2019, at 12:42, Torbjörn Granlund wrote: > > Apple has released a new version of Xcode. It is said to fix some issue > with UITextView, and as the update size is 8 GiB UITextView must be a > very large function. > > But hopefully they also managed to fix the C compiler to

Re: macOS Catalina: FAIL: t-powm

> On 16 Nov 2019, at 10:14, Torbjörn Granlund wrote: > > There is a non-zero probability that these GMP test suite failures are > caused by bugs in GMP. We cannot tell for sure, as we have not isolated > the failures. Or maybe just the test suite, as suggested som other post?! > And as gdb

Re: macOS Catalina: FAIL: t-powm

> On 16 Nov 2019, at 14:21, Jack Howarth > wrote: > >> > And as gdb no longer >> > works on Macos, I would feel like a beginner programmer again. >> >> There is “native” lldb, which should work with GCC, too, I think. > > Just to be clear, the 'gcc' on recent macOS has always been stub

Re: macOS Catalina: FAIL: t-powm

> On 16 Nov 2019, at 14:21, Jack Howarth > wrote: > > The gmp package in MacPorts relies on always building with the core2 > architecture in order ship uniform packaging of gmp for all Intel based Macs. > That is why everyone sees the same glitch in Xcode 11 who is using MacPorts. The make

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 8 Nov 2019, at 15:48, Torbjörn Granlund wrote: > > There is info here, suggesting > uninitialized memory access in the test suite: > https://lists.llvm.org/pipermail/cfe-users/2019-November/001640.html > > What are you trying to contribute to the discussion in the Subject line? > >

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 20 Oct 2019, at 22:14, Torbjörn Granlund wrote: > > Believe it or not, but the GMP devs are pretty good at computer > arithmetic. How about memory allocations? — There is info here, suggesting uninitialized memory access in the test suite:

Re: GMP and Macos Catalina

> On 15 Dec 2019, at 00:45, Torbjörn Granlund wrote: > > Hans Åberg writes: > >> On 14 Dec 2019, at 23:49, Torbjörn Granlund wrote: >> >> Many people have reported problems with GMP on Macos Catalina. >> >> The problem now seems to h

Re: GMP and Macos Catalina

> On 14 Dec 2019, at 23:49, Torbjörn Granlund wrote: > > Many people have reported problems with GMP on Macos Catalina. > > The problem now seems to have been fixed with the Xcode 11.3 release. At least the tests pass: One error with clang 9.0.0 of MacPorts (using gmp-6.1.2), which should be

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 20 Oct 2019, at 13:24, Torbjörn Granlund wrote: > > Hans Åberg writes: > > I have compiled gmp-6.1.2 on MacOS 10.15 using the inhouse Apple clang > and the MacPorts gcc9 and clang9, with ‘make check’. All tests passed > on gcc9, but the two clang had one err

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 20 Oct 2019, at 21:44, Torbjörn Granlund wrote: > > Hans Åberg writes: > > A common programming error is assuming that signed integer types are > two’s complement, because even though all current CPUs are that, > overflows are undefined in C/C++, and an optimiz

Re: Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

> On 20 Oct 2019, at 22:14, Torbjörn Granlund wrote: > > Hans Åberg writes: > >> I believe we assume signed integers are in two's complement. > > Strictly, it is for signed overflows one cannot assume modulo 2^n, n = > number of bits. For the unsigned i

Report: gmp-6.1.2 on MacOS 10.15 using GCC and two Clang

I have compiled gmp-6.1.2 on MacOS 10.15 using the inhouse Apple clang and the MacPorts gcc9 and clang9, with ‘make check’. All tests passed on gcc9, but the two clang had one error each. % uname -a Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019;

Re: Latest commit introduces undefined behavior in hgcd2.c

> On 18 Sep 2019, at 21:37, Niels Möller wrote: > > …a problem, at least in theory, if it is "undefined behavior". I'm afraid I > don't know these fine details of the C spec by heart. It is undefined behavior according to the section “Shift operators” in

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

> On 8 Oct 2019, at 23:59, Torbjörn Granlund wrote: > > Juergen Reuter writes: > > Please let me know any further information you need. > > This is almost surely a compiler bug. We have encountered countless of > bugs in clang since it showed up. We have up-to-date apple systems for >

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

ed 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 know any further inf

Re: GMP bug (?) - unable to build for ARM64 with assembly enabled

> On 14 Oct 2020, at 12:59, Andreas Buff wrote: > > We are cross building GMP for use on ARM64 iOS devices using this command: > … This link suggests using the -target option for makefiles outside Xcode. https://developer.apple.com/documentation/xcode/building_a_universal_macos_binary

Re: gmp 6.2.0 documentation bug

> On 29 Sep 2020, at 19:17, Marco Bodrato wrote: > > Il 2020-09-29 16:09 TonyMcC ha scritto: >> I think there is a word (a function name?) missing from the >> documentation for gmp 6.2.0. In gmp.texi, at line 2541 it reads: >> "it's probably best to call to get a starting point and iterate

Re: Linking failure on aarch64

> On 2 Jul 2020, at 00:49, Torbjörn Granlund wrote: > > (I actually attempted installing Apple's compiler bundle "Xcode" with > support for arm64, in order to work out some of these issues. > Unfortunately, Apple's documentaton was too lacking for a successful > install.) Exactly what did not

Re: Linking failure on aarch64

> On 2 Jul 2020, at 16:15, Torbjörn Granlund wrote: > > Hans Åberg writes: > >> On 2 Jul 2020, at 00:49, Torbjörn Granlund wrote: >> >> (I actually attempted installing Apple's compiler bundle "Xcode" with >> support for arm64, in order to w

Re: Linking failure on aarch64

> On 2 Jul 2020, at 20:53, Torbjörn Granlund wrote: > > Hans Åberg writes: > > One must run 'xcode-select install' from the Terminal. > > I came that far (except it is --install) before giving up. Right. > But --install is not for installing a new Xcode, but for i

Re: Linking failure on aarch64

> On 2 Jul 2020, at 21:23, Torbjörn Granlund wrote: > > Hans Åberg writes: > > So here it should be >xcode-select --switch /Applications/Xcode-beta.app/Contents/Developer > > Sorry, I must have been unclear. I lacked installation instructions for > how

Re: Constructor taking 64-bit integer missing on (some) Windows C++ compilers

> On 6 Jun 2020, at 06:28, Mihai Preda wrote: > > At this point the C++ compiler on windows (where long is 32-bit) > reports errors, see at the end. The problem is that the set of > constructors does not include one taking a 64-bit integer: > > #define __GMPXX_DEFINE_ARITHMETIC_CONSTRUCTORS

Re: uint_least32_t is in stdint.h not in inttypes.h

> On 16 Nov 2020, at 10:53, Torbjörn Granlund wrote: > > Vincent Lefevre writes: > > So, including if present should be sufficient, and > this is what the above code does. > > That said, for C99 implementations, the #if tests would be useless, > so that the above code is also designed

Re: GMP bootstrap fails with Autoconf 2.69d

> On 16 Nov 2020, at 01:18, Vincent Lefevre wrote: > > On 2020-11-15 23:49:10 +0100, Hans Åberg wrote: >> One can also have an additional URL argument, which defines a variable >> PACKAGE_URL: >> >> AC_INIT(GNU MP, GMP_VERSION, [gmp-bugs@gmplib.org (see >&

Re: GMP bootstrap fails with Autoconf 2.69d

> On 16 Nov 2020, at 11:41, Vincent Lefevre wrote: > > On 2020-11-16 10:29:13 +0100, Hans Åberg wrote: >>> On 16 Nov 2020, at 01:18, Vincent Lefevre wrote: >>> If I understand correctly, the goal is to have the Reporting-Bugs.html >>> URL together

Re: possible miscompilation on macOS Catalina 10.15.6

> On 28 Oct 2020, at 12:24, Trevor Spiteri wrote: > > Sorry for not being clearer: I was only concerned that there was a > chance the combination > > configure --enable-fat --disable-shared --with-pic > > might cause issues with Catalina's default compiler, if there even is > such a

Re: Build error using pre-packaged GMP

> On 26 May 2021, at 10:31, Marc Glisse wrote: > > My first guess would be some misguided > > extern "C" { > #include > } Indeed it is, testing with g++ 11. The errors that the OP posted arrive at the end, the first, not posted, error is: /opt/local/include/gcc11/c++/bits/memoryfwd.h:63:3:

Re: small patch to suppress a warning

> On 10 Feb 2021, at 23:55, Stephan Pleines wrote: > > Can you please elaborate why it is a compiler bug? It is a legal C feature, so there should not be issued a warning. ___ gmp-bugs mailing list gmp-bugs@gmplib.org

Re: small patch to suppress a warning

You do not say which compiler it is, but it looks like a clang bug. > On 10 Feb 2021, at 17:26, Stephan Pleines wrote: > > Hi, > > This is a tiny patch to suppress a warning about operator precedence. > > Thank you, > Stephan > > diff -r 925753a1f950 mpz/pprime_p.c > --- a/mpz/pprime_p.c

Re: Build failure on macOS Sonoma 14.0 beta

> On 20 Sep 2023, at 22:45, Marc Culler wrote: > > I learned by reading the release notes for XCode 15 that Apple rewrote the > linker for XCode 15. They also made the old linker available by using -ld64 > as a linker option. When I use the new linker, using MacPorts gcc12 and gmp-6.2.1, I

Re: Build failure on macOS Sonoma 14.0 beta

> On 20 Sep 2023, at 16:36, Marc Culler wrote: > > …macOS Sonoma beta… … > …using: "Apple clang version 15.0.0 > (clang-1500.0.40.1)" The same compiler version is now available on MacOS 13, together with Xcode 15. ___ gmp-bugs mailing list

Re: Build failure on macOS Sonoma 14.0 beta

> On 22 Sep 2023, at 00:10, Marc Culler wrote: > > This appears to be a completely independent bug in Apple's new linker. (You > are linking with libgmp, but presumably that library was built with a > different linker. And the "error" is different.) It may be because I use atomic code,

Re: Build failure on macOS Sonoma 14.0 beta

> On 20 Sep 2023, at 22:45, Marc Culler wrote: > > I learned by reading the release notes for XCode 15 that Apple rewrote the > linker for XCode 15. They also made the old linker available by using -ld64 > as a linker option. One should use -ld_classic as -ld64 is deprecated by a warning I

Re: GMP 6.2.1 core2 x86_64 assembler error "operands invalid for `movq'"

> On 1 Nov 2022, at 22:55, Torbjörn Granlund wrote: > > Is this on a recent version of macos with current versions gcc+binutils > installed? Or is either old variants? Darwin 11.4.2 is OS X 10.7.5 Lion from September 19, 2012. https://en.wikipedia.org/wiki/OS_X_Lion