Re: Configuration on IceLake

2021-10-13 Thread Torbjörn Granlund
Arturo Fernandez  writes:

  Just for clarification, I'm no longer seeing the 'm4-ccas: Permission
  denied' error. I started on a fresh system (cloud-based) running
  CentOS8.4, unpacked gmp-6.2.99-20211010014524 and simply run
  ./configure, which returned:
  Version: GNU MP 6.2.99
  Host type: nehalem-pc-linux-gnu

What evidence do you have for this system being an Ice Lake?

And even if it is, you're presumably using a virtualised system (being
in "the cloud") and virtualisers are sometimes configured to pretend the
CPU is of a different type than they actually are.

  This was my original problem, which is that configure is not picking
  up IceLake and assigning nehalem to the host type. I'm not sure if the
  GMPLIB Team is testing these new patches on IceLake HW but it might be
  worth considering before releasing a stable version.

Sneer will not inspire us helping you.

It might be the case that GMP doesn't recognise every family/model which
Intel uses for Ice lake.  If you show us that the cpuid instruction
returns for you system, then we can tell where the problem lies.

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


Re: Configuration on IceLake

2021-10-13 Thread Arturo Fernandez
Hi Torbjörn,
Just for clarification, I'm no longer seeing the 'm4-ccas: Permission denied' 
error. I started on a fresh system (cloud-based) running CentOS8.4, unpacked 
gmp-6.2.99-20211010014524 and simply run ./configure, which returned:
Version: GNU MP 6.2.99
Host type: nehalem-pc-linux-gnu
ABI: 64
Install prefix: /usr
Compiler: gcc
Static libraries: yes
Shared libraries: yes 
This was my original problem, which is that configure is not picking up IceLake 
and assigning nehalem to the host type. I'm not sure if the GMPLIB Team is 
testing these new patches on IceLake HW but it might be worth considering 
before releasing a stable version.
Thanks,
Arturo

Torbjörn Granlund wrote:
Arturo Fernandez mailto:afernan...@odyhpc.com> > writes:
Hello. I was finally able to get back and work on this
configuration. Yesterday evening I downloaded the latest version
(gmp-6.2.99-20211010014524) but it is still unable to recognize
IceLake. The command configure is returning:
Version: GNU MP 6.2.99
Host type: nehalem-pc-linux-gnu
ABI: 64
Install prefix: /usr
Compiler: gcc
Static libraries: yes
Shared libraries: yes
It is hard to provide support when the context is lost due do months
long delays.
I am sorry you keep seeing problems with executing exeutable GMP scripts
on several systems. It is an unusual problem, and not something we can
fix on the GMP side. We cannot make these scripts "more exeutable".
As I believe I told you, the few times we have had this reported, it has
been caused by ether a poorly chosen umask during tar file extraction,
or filesystem policy against executables. Both these problems are with
your setup, not with GMP.
You need to debug this locally, if needed with some local help.
-- 
Torbjörn
Please encrypt, key id 0xC8601622
___
gmp-bugs mailing list
gmp-bugs@gmplib.org
https://gmplib.org/mailman/listinfo/gmp-bugs


Re: Configuration on IceLake

2021-10-13 Thread Torbjörn Granlund
Arturo Fernandez  writes:

  Hello. I was finally able to get back and work on this
  configuration. Yesterday evening I downloaded the latest version
  (gmp-6.2.99-20211010014524) but it is still unable to recognize
  IceLake. The command configure is returning:
  Version: GNU MP 6.2.99
  Host type: nehalem-pc-linux-gnu
  ABI: 64
  Install prefix: /usr
  Compiler: gcc
  Static libraries: yes
  Shared libraries: yes

It is hard to provide support when the context is lost due do months
long delays.

I am sorry you keep seeing problems with executing exeutable GMP scripts
on several systems.  It is an unusual problem, and not something we can
fix on the GMP side.  We cannot make these scripts "more exeutable".

As I believe I told you, the few times we have had this reported, it has
been caused by ether a poorly chosen umask during tar file extraction,
or filesystem policy against executables.  Both these problems are with
your setup, not with GMP.

You need to debug this locally, if needed with some local help.

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