Re: Make check fails on samsung S8 (2)

2020-10-28 Thread Marco Bodrato

Ciao Marc,

Il 2020-08-22 19:39 Marc Glisse ha scritto:

Ah, on your OS nl_langinfo is defined inline as a static function in
langinfo.h, so the hack used in the test of redefining the function
cannot work. I guess we are supposed to add some configure check that
nl_langinfo can be redefined... although for just one platform we
could add a simple #if like we already do for mingw, so the test is
skipped.


Are you suggesting something like the following?

diff -r 3328dc92960a tests/misc/t-locale.c
--- a/tests/misc/t-locale.c Sun Oct 25 22:14:38 2020 +0100
+++ b/tests/misc/t-locale.c Thu Oct 29 02:43:25 2020 +0100
@@ -57,7 +57,7 @@
 #endif

 /* Replace the libc nl_langinfo with one we can manipulate. */
-#if HAVE_NL_LANGINFO
+#if HAVE_NL_LANGINFO && ! defined __TERMUX__
 char *
 nl_langinfo (nl_item n)
 #if defined __cplusplus && defined __GLIBC__

Ĝis,
m
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs


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

2020-10-28 Thread Andreas Buff


Am 16.10.20 um 11:48 schrieb Torbjörn Granlund:
> Andreas Buff  writes:
>
>thanks to your help, its building fine now without --disable-assembly,
>but it crashes using it.
>
>I am totally not into ASM, so forgive unqualified report(s).
>
>Here is the backtrace:
>
>* thread #8, queue = 'PEPAsyncSession.queue', stop reason =
>EXC_BAD_ACCESS (code=2, address=0x16fbcc000)
>   * frame #0: 0x0001019baf58 PEPObjCAdapterFramework`__gmpn_add_n + 
> 144
>     frame #1: 0x0001019babe4 PEPObjCAdapterFramework`__gmpn_add + 68
>     frame #2: 0x0001019e756c
>PEPObjCAdapterFramework`__gmpn_toom2_sqr + 1020
>     frame #3: 0x0001019c8030 PEPObjCAdapterFramework`__gmpn_sqr + 144
>     frame #4: 0x0001019fe838 PEPObjCAdapterFramework`__gmpn_powm + 
> 3416
>     frame #5: 0x0001019b5678 PEPObjCAdapterFramework`__gmpz_powm + 
> 2432
>
>Let me know if and how to provide more useful information if needed.
>
> Your report is scarce of detail.  Perhaps there is a bug in your
> program?
>
> Another possibility is that GMP does not work right on Ios.  Since that
> is a closed platform where developers need to pay Apple for programming,
> you cannot excpect any effort from the GMP team with regards to
> development or testing of GMP for Ios.
>
> If somebody who pays the Apple programmer tax is willing to help you
> debug your crash, we will certainly look at whatever GMP change might be
> needed.
>
Haha, fair enough, thanks :-)

JFYI: I can confirm GMP works fine on iOS with ASM disabled.





pEpkey.asc
Description: application/pgp-keys
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs


Re: possible miscompilation on macOS Catalina 10.15.6

2020-10-28 Thread Torbjörn Granlund
Trevor Spiteri  writes:

  I maintain Rust language bindings to GMP and got a bug report from a
  user on macOS Catalina 10.15.6.  I do not know if this issue is caused
  by the particular system setup of the user or if it is more general, so
  I'm listing what information I have in case it is actually reproducible
  in a more general setting.

  The bindings compilation process compiles GMP using:

  ln -s path/to/extracted/gmp-6.2.0 gmp-src
  mkdir gmp-build
  cd gmp-build
  ../gmp-src/configure --enable-fat --disable-shared --with-pic
  make -j 8
  make -j 8 check

  The make check is failing and outputting this on standard error:

  ../../../gmp-src/test-driver: line 107: 4825 Segmentation fault: 11 "$@"
  > $log_file 2>&1
  make[5]: *** [test-suite.log] Error 1
  make[4]: *** [check-TESTS] Error 2
  make[3]: *** [check-am] Error 2
  make[2]: *** [check-recursive] Error 1
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2

  I don't have standard output, so I don't know which test actually failed.

  This is all the information I got; sorry if it is incomplete. (The
  user's issue was solved by using their already installed homebrew?
  libraries instead of compiling GMP anew.)

OK, so *some* compiler compiled GMP with and *some* GMP test program
reported a segfault.  I will right away start the natural deduction over
all possible instances of compilers and GMP test cases. Oh wait, I need
to consider all possible CPUs and relevant environment variables as
well.


-- 
Torbjörn
Please encrypt, key id 0xC8601622
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs


possible miscompilation on macOS Catalina 10.15.6

2020-10-28 Thread Trevor Spiteri
I maintain Rust language bindings to GMP and got a bug report from a
user on macOS Catalina 10.15.6.  I do not know if this issue is caused
by the particular system setup of the user or if it is more general, so
I'm listing what information I have in case it is actually reproducible
in a more general setting.

The bindings compilation process compiles GMP using:

ln -s path/to/extracted/gmp-6.2.0 gmp-src
mkdir gmp-build
cd gmp-build
../gmp-src/configure --enable-fat --disable-shared --with-pic
make -j 8
make -j 8 check

The make check is failing and outputting this on standard error:

../../../gmp-src/test-driver: line 107: 4825 Segmentation fault: 11 "$@"
> $log_file 2>&1
make[5]: *** [test-suite.log] Error 1
make[4]: *** [check-TESTS] Error 2
make[3]: *** [check-am] Error 2
make[2]: *** [check-recursive] Error 1
make[1]: *** [check-recursive] Error 1
make: *** [check] Error 2

I don't have standard output, so I don't know which test actually failed.

This is all the information I got; sorry if it is incomplete. (The
user's issue was solved by using their already installed homebrew?
libraries instead of compiling GMP anew.)


___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs