Re: [sage-devel] deterministic "ordering" of subsets (py3)

2018-11-07 Thread Vincent Delecroix

Python 3 introduced randomness in their base hashing functions. That
impact strings.

$ python -c 'print(hash("hello Daniel!"))'
-4203807413548925149
$ python -c 'print(hash("hello Daniel!"))'
7756578277334792321

Vincent



Vincent

Le 06/11/2018 à 14:58, Daniel Krenn a écrit :

I just was hunting a Heisenbug related to Python3. It boils down to the
following:

dakrenn@nops:~$ /opt/sage/8.5.beta2-python3/sage -c "P. = QQ[]; S
= Set([x,y,z]).subsets(2); print(S); print(list(S))"
Subsets of {y, x, z} of size 2
[{x, y}, {z, y}, {z, x}]
dakrenn@nops:~$ /opt/sage/8.5.beta2-python3/sage -c "P. = QQ[]; S
= Set([x,y,z]).subsets(2); print(S); print(list(S))"
Subsets of {z, x, y} of size 2
[{z, x}, {z, y}, {x, y}]
dakrenn@nops:~$ /opt/sage/8.5.beta2-python3/sage -c "P. = QQ[]; S
= Set([x,y,z]).subsets(2); print(S); print(list(S))"
Subsets of {y, x, z} of size 2
[{y, x}, {y, z}, {x, z}]

So the order in which the subsets appear is random (and also the order
in the sets). I was wondering why this order is *now* (Python3) random,
but was not before:

dakrenn@nops:~$ sage -c "P. = QQ[]; S = Set([x,y,z]).subsets(2);
print(S); print(list(S))"
Subsets of {y, z, x} of size 2
[{y, z}, {y, x}, {z, x}]

The result in Python2-SageMath was the same for roughly 10 runs (for
Python3 above, three runs three different results).

(My question is also because there is an order on the elements
themselves, namely z < y < x. And I am aware that sets are unordered so
ordering is not to be expected, but still there is this change and I was
wondering why (as the elements themselves are still comparable in
Python3-SageMath.)

Daniel



--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] How to pass TARGET=ZEN to OpenBLAS's Makefile?

2018-11-07 Thread Dima Pasechnik
Try running

OPENBLAS_CONFIGURE="TARGET=ZEN"  make -j9




On Wed, Nov 7, 2018 at 2:12 PM Brenton Horne  wrote:
>
> Hi folks
>
> Is there a way to pass a variable to OpenBLAS's Makefile? OpenBLAS fails to 
> compile for me against my AMD Ryzen 7 2700 processor, thanks to this issue 
> https://github.com/xianyi/OpenBLAS/issues/1242 (full log is attached). I've 
> tried running:
> TARGET=ZEN make -j9
> in the top level directory of SageMath's master branch, but I always get this 
> OpenBLAS error. I've tried manually building this dep myself in the 
> local/var/tmp/sage/build/openblas-0.2.20.p2 subdirectory and then running:
> TARGET=ZEN make PREFIX=/path/to/sage-git-repo/local install
> and it builds fine. Therefore, as passing this to SageMath's Makefile doesn't 
> build OpenBLAS correctly I'm guessing the TARGET=ZEN isn't being correctly 
> passed to OpenBLAS's build by SageMath's Makefile. If you're thinking merely 
> running the make command in sage's top level directory after manually and 
> successfully building and installing (with the aforementioned make PREFIX 
> command) OpenBLAS would fix this, I've tried that and I still get this build 
> error.
>
> Thanks for your time and help,
> Brenton
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Sage 8.4 does not compile / CentOS 6.10

2018-11-07 Thread Daniel Ouimet
I did what you suggest:
installing a newer version.  The newest I could find for my CentOS is:
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)

Then for the first time it goes further and further.  Took hours!  but it 
finally stopped there (also in attachment the log file):

[fflas_ffpack-2.3.2] In file included from 
../../../fflas-ffpack/fflas/fflas_simd.h:208:0,
[fflas_ffpack-2.3.2]  from 
../../../fflas-ffpack/fflas/fflas_freduce.h:33,
[fflas_ffpack-2.3.2]  from 
../../../fflas-ffpack/fflas/fflas.h:104,
[fflas_ffpack-2.3.2]  from fflas_L1_inst.C:34:
[fflas_ffpack-2.3.2] ../../../fflas-ffpack/fflas/fflas_simd/simd256.inl: In 
static member function 'static Simd256i_base::vect_t 
Simd256i_base::sll128(Simd256i_base::vect_t)':
[fflas_ffpack-2.3.2] 
../../../fflas-ffpack/fflas/fflas_simd/simd256.inl:102:85: error: there are 
no arguments to '_mm256_bslli_epi128' that depend on a template parameter, 
so a declaration of '_mm256_bslli_epi128' must be available [-fpermissive]
[fflas_ffpack-2.3.2]   static INLINE CONST vect_t sll128(const vect_t a) { 
return _mm256_bslli_epi128(a, s); }
[fflas_ffpack-2.3.2]
  
^
[fflas_ffpack-2.3.2] 
../../../fflas-ffpack/fflas/fflas_simd/simd256.inl:102:85: note: (if you 
use '-fpermissive', G++ will accept your code, but allowing the use of an 
undeclared name is deprecated)
[fflas_ffpack-2.3.2] ../../../fflas-ffpack/fflas/fflas_simd/simd256.inl: In 
static member function 'static Simd256i_base::vect_t 
Simd256i_base::srl128(Simd256i_base::vect_t)':
[fflas_ffpack-2.3.2] 
../../../fflas-ffpack/fflas/fflas_simd/simd256.inl:110:85: error: there are 
no arguments to '_mm256_bsrli_epi128' that depend on a template parameter, 
so a declaration of '_mm256_bsrli_epi128' must be available [-fpermissive]
[fflas_ffpack-2.3.2]   static INLINE CONST vect_t srl128(const vect_t a) { 
return _mm256_bsrli_epi128(a, s); }
[fflas_ffpack-2.3.2]
  
^
[fflas_ffpack-2.3.2] make[8]: *** [fflas_L1_inst.lo] Error 1
[fflas_ffpack-2.3.2] make[8]: Leaving directory 
`/usr/local/soft/sage-8.4/local/var/tmp/sage/build/fflas_ffpack-2.3.2/src/fflas-ffpack/interfaces/libs'
[fflas_ffpack-2.3.2] make[7]: *** [all-recursive] Error 1
[fflas_ffpack-2.3.2] make[7]: Leaving directory 
`/usr/local/soft/sage-8.4/local/var/tmp/sage/build/fflas_ffpack-2.3.2/src/fflas-ffpack/interfaces'
[fflas_ffpack-2.3.2] make[6]: *** [all-recursive] Error 1
[fflas_ffpack-2.3.2] make[6]: Leaving directory 
`/usr/local/soft/sage-8.4/local/var/tmp/sage/build/fflas_ffpack-2.3.2/src/fflas-ffpack'
[fflas_ffpack-2.3.2] make[5]: *** [all-recursive] Error 1
[fflas_ffpack-2.3.2] make[5]: Leaving directory 
`/usr/local/soft/sage-8.4/local/var/tmp/sage/build/fflas_ffpack-2.3.2/src'
[fflas_ffpack-2.3.2] make[4]: *** [all] Error 2
[fflas_ffpack-2.3.2] make[4]: Leaving directory 
`/usr/local/soft/sage-8.4/local/var/tmp/sage/build/fflas_ffpack-2.3.2/src'
[fflas_ffpack-2.3.2] 

[fflas_ffpack-2.3.2] Error building fflas_ffpack-2.3.2
[fflas_ffpack-2.3.2] 



Any other suggestions

Thanks
Daniel

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Found local metadata for fflas_ffpack-2.3.2
Using cached file /usr/local/soft/sage-8.4/upstream/fflas_ffpack-2.3.2.tar.bz2
fflas_ffpack-2.3.2

Setting up build directory for fflas_ffpack-2.3.2
Finished extraction
Applying patches from ../patches...
Applying ../patches/25353-fflasffpack-constvoid.patch
patching file fflas-ffpack/fflas/fflas_simd/simd256_int16.inl
patching file fflas-ffpack/fflas/fflas_simd/simd256_int32.inl
patching file fflas-ffpack/fflas/fflas_simd/simd256_int64.inl

Host system:
Linux boole.CRM.UMontreal.CA 2.6.32-754.2.1.el6.x86_64 #1 SMP Fri Jul 13 
12:50:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

C compiler: /opt/rh/devtoolset-2/root/usr/bin/gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=/opt/rh/devtoolset-2/root/usr/bin/gcc
COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/opt/rh/devtoolset-2/root/usr 
--mandir=/opt/rh/devtoolset-2/root/usr/share/man 

[sage-combinat-devel] Coding sprints at IMA

2018-11-07 Thread Anne Schilling
Dear All!

The IMA is soliciting applications for coding sprints for teams of 2-8 
participants to spend 3-5 days at the IMA
to work on Sage or Macaulay2. For details, see

https://www.ima.umn.edu/2018-2019/SW7.22-26.19

Please apply if you are interested!

Best wishes,

Anne

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Coding Sprints at IMA

2018-11-07 Thread Anne Schilling
Dear All!

The IMA is soliciting applications for coding sprints for teams of 2-8 
participants to spend 3-5 days at the IMA
to work on Sage or Macaulay2. For details, see

https://www.ima.umn.edu/2018-2019/SW7.22-26.19

Please apply if you are interested!

Best wishes,

Anne

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.