On Thu, 24 Aug 2023, Torbjörn Granlund wrote:
Marc Glisse writes:
There is, it is called (u)intptr_t, the standard name for an integer
type that can hold a pointer.
Right!
I only naively checked intmax_t, assuming max would mean max. :-)
Hmm, for old ABIs gaining a new integer type, I
Marc Glisse writes:
There is, it is called (u)intptr_t, the standard name for an integer
type that can hold a pointer.
Right!
I only naively checked intmax_t, assuming max would mean max. :-)
There seem to be a problem with arithmetic on uintptr_t, though. The
compiler generates a plain
On Thu, 24 Aug 2023, Torbjörn Granlund wrote:
Note the size of pointers, 16 bytes. There is no integer type mathing
that, so if code tries to cast a pointer through some integer type for,
say, aligning it, things will break.
There is, it is called (u)intptr_t, the standard name for an
Marc Glisse writes:
Hmm, but with that proposed patch, configure later fails with
checking size of void *... 16
checking size of unsigned short... 2
checking size of unsigned... 4
checking size of unsigned long... 8
checking size of mp_limb_t... 8
configure: error: Oops, mp_limb_t
On Thu, 24 Aug 2023, Marc Glisse wrote:
It seems that uname -p returns aarch64c, configfsf.guess uses that, and
configfsf.sub gets confused by that, so it should be reported there. Ah, I
already see at least
https://lists.gnu.org/archive/html/config-patches/2023-08/msg00043.html
so hopefully
It seems that uname -p returns aarch64c, configfsf.guess uses that, and
configfsf.sub gets confused by that, so it should be reported there. Ah, I
already see at least
https://lists.gnu.org/archive/html/config-patches/2023-08/msg00043.html
so hopefully it will get discussed / solved there.
On
Hi,
gmp 6.3.0 does not compile on this machine:
zimmerma@cfarm240:~/gmp-6.3.0 $ ./configure
checking build system type... Invalid configuration
'aarch64c-unknown-freebsd14.0': machine 'aarch64c-unknown' not recognized
configure: error: /bin/sh ./config.sub aarch64c-unknown-freebsd14.0
