Sage 8.9.beta5 released

Volker Braun

unread,

Aug 3, 2019, 7:56:05 AM8/3/19

to sage-release

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

ac8cf16c5c (tag: 8.9.beta5, trac/develop) Updated SageMath version to 8.9.beta5

73d2ad18c0 Trac #27819: Poset(), error checking when linear_extension=True

db426b3de5 Trac #28310: some changes in a few while

0d67ce1f41 Trac #28303: better string representation of Macaulay2 elements

9d327f005e Trac #28301: remove deprecated method immediate_dominators

042137ad3b Trac #28300: py3: fix last 2 doctests in French book

75ff484366 Trac #28290: remove some deprecated stuff in graphs and digraphs

0ad39b9a9c Trac #28277: py3: add the graphs/ folder to known passing

d951d9499d Trac #28225: Allow sage to run in the absence of sage-env

79a719845f Trac #28221: minor improvement in bidirectional_dijkstra

a62d7fa54e Trac #28195: Implement LexUP and LexDOWN

74b6587a59 Trac #27875: Cythonize line_graph

e1de3839b2 Trac #28296: Random failure in src/sage/rings/qqbar.py

564f26fe5f Trac #28200: reduce base field for scheme morphisms

d825f97db1 Trac #28023: matplotlib 2.2.4 + patches

92ff95d408 Trac #27692: py3: fix src/sage/misc/nested_class.pyx

27a54e331a Trac #26932: Upgrade to givaro-4.1.1 fflas-ffpack-2.4.3 linbox-1.6.3

3caf34d332 Trac #23813: Implement matrix action on polynomial scheme morphisms

faa92bddc6 Trac #28208: spkg-configure.m4 for symmetrica

97fb8a6a43 Trac #27827: spkg-configure.m4 for pkgconf

4cc096527a Trac #28268: some typos in combinat

db35be1dca Trac #28260: Fix typo commmand -> command

9b8b6c4061 Trac #28267: a small typo ticket

3f60aae59a Trac #28232: py3: fix doctests in doctest/test

729d504608 Trac #28137: Fix broken link on Git setup page in Developer's Guide

b4d255ca65 Trac #28123: Implement method to return the p-primary part of an integer

6916817f00 Trac #28071: Enhance global_height functionality for other fields

36f9e45109 Trac #27984: Coersion of inputs of orbit into projective space

1519de3f6a Trac #28266: Improve speed of diagram algebra multiplication

07314c1b48 Trac #28256: add .is_self_dual method for polytopes

ab950f0e69 Trac #28253: Fixing method "is_SPP()" for plane partition

3237170bc2 Trac #28240: Move rational methods of the backend normaliz to the `_QQ` class

bc9b5e20b8 Trac #28236: add a way to restrict an index face set

5d6531f38b Trac #28235: py3: polyhedron folder with optional packages

504977080b Trac #28233: fix doctest in gap_packages when ~/.gap is not empty

6688d1b1d4 Trac #28227: py3 fixes for weyl_characters.py

75b5ab2aca Trac #28217: awali spkg-install wrong on Python 3

4aa32b980d Trac #28204: p_group_cohomology version 3.2

034d7f8bec Trac #28188: MeatAxe arithmetic tables

d9e5056677 Trac #27993: Make outer normal fans readily available

9e9a2a4c6b Trac #27987: CombinatorialPolyhedron improve initialization, remove bug for unbounded polyhedra

1537fe511b (tag: 8.9.beta4) Updated SageMath version to 8.9.beta4

David Coudert

unread,

Aug 3, 2019, 8:41:28 AM8/3/19

to sage-r...@googlegroups.com

Some tickets included in this release are still marked as « positive review » on trac.

See for instance https://trac.sagemath.org/ticket/28195

Is it normal ?

--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/27e5d274-fcb3-421d-810d-fb7781afc2af%40googlegroups.com.

John H Palmieri

unread,

Aug 3, 2019, 6:46:30 PM8/3/19

to sage-release

New failure with Python 3:

sage -t --warn-long 78.7 src/sage/tests/cmdline.py
**********************************************************************
File "src/sage/tests/cmdline.py", line 503, in sage.tests.cmdline.test_executable
Failed example:
    print(err)
Expected:
    Cython (http://cython.org) is a compiler for code written in the
    Cython language.  Cython is based on Pyrex by Greg Ewing.
    ...
Got:
    Traceback (most recent call last):
      File "/Users/palmieri/Desktop/Sage_stuff/sage_builds/PYTHON3/sage-8.9.beta5/src/bin/sage-cython", line 12, in <module>
        from sage.env import SAGE_SRC
    ImportError: No module named sage.env
    <BLANKLINE>

This is because of https://trac.sagemath.org/ticket/28225.

Volker Braun

unread,

Aug 3, 2019, 7:53:02 PM8/3/19

to sage-release

Fixed!

To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

Markus Wageringel

unread,

Aug 5, 2019, 4:17:46 PM8/5/19

to sage-release

The package fflas_ffpack-2.4.3 added in #26932 fails to compile for me on CentOS 7.6.1810, due to several errors of this form:

g++: error: unrecognized command line option '-mavx512f'
g++: error: unrecognized command line option '-mavx512vl'
g++: error: unrecognized command line option '-mavx512dq'

The log file is attached.

fflas_ffpack-2.4.3.log

Dima Pasechnik

unread,

Aug 5, 2019, 4:23:04 PM8/5/19

to sage-release

You're using gcc version 4.8.5, released in 2015. I guess AVX 512
didn't exist yet.

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/ec04cd37-c65e-411f-886f-5e58a45a89a4%40googlegroups.com.

François Bissey

unread,

Aug 5, 2019, 5:05:31 PM8/5/19

to 'Justin C. Walker' via sage-release

But fflas-ffpack detection routines pick it up when they shouldn’t. Technically I see that
as an upstream inbox team problem since they share their detection routines over the entire
givaro/fflas-ffpack/linbox stack.
You may want to try
export FFLAS_FFPACK_CONFIGURE=“—disable-fma —disable-fma4 —disable-avx —disable-avx2”
and then run make again. But you may have to do a similar stop when building linbox.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAAWYfq3dycsV39S-WW%3DSHXi8nYfWSm7Lv_me9ACoPKBp2Pboxg%40mail.gmail.com.

Markus Wageringel

unread,

Aug 5, 2019, 5:49:53 PM8/5/19

to sage-release

Thank you for the quick replies. It is the system's default compiler – no idea why it is so old.

export FFLAS_FFPACK_CONFIGURE="-disable-fma -disable-fma4 -disable-avx -disable-avx2"

Hm, that did not work, giving still the same error for fflas-ffpack. I assume I would have to disable AVX 512 as well?

Though, I guess it is better to have it than not. Using gcc 8.3.1 from devtoolset-8 works successfully.

François Bissey

unread,

Aug 5, 2019, 6:05:12 PM8/5/19

to sage-r...@googlegroups.com

After inspection of configure they are all brand new options I didn’t know anything
about. That would have been —disable-{avx512f,avx512dq,avx512vl}. I am still shocked
it enabled them without your compiler supporting it. The logic must be flawed.
In any case we need to add those to the list of disabled options in fat binary builds.
It would have been nice to have the config log from when you had the failure.

François

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/28c5affc-5613-4a0c-8d92-0daf385a982b%40googlegroups.com.

Markus Wageringel

unread,

Aug 5, 2019, 6:26:57 PM8/5/19

to sage-release

It would have been nice to have the config log from when you had the failure.

Would you still like to have it? I could reproduce it I suppose.

François Bissey

unread,

Aug 5, 2019, 6:28:29 PM8/5/19

to sage-r...@googlegroups.com

Yes I would like to see it. I have looked at what fflas-ffpack does to detect
the stuff but I want a practical output for that case.

> On 6/08/2019, at 10:26 AM, Markus Wageringel <markus.w...@gmail.com> wrote:
>
> It would have been nice to have the config log from when you had the failure.
>
> Would you still like to have it? I could reproduce it I suppose.
>

> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/2804df41-26e7-4820-93e6-35e7cb031bf5%40googlegroups.com.

Markus Wageringel

unread,

Aug 6, 2019, 1:31:14 AM8/6/19

to sage-release

The config.log is attached.

Am Dienstag, 6. August 2019 00:28:29 UTC+2 schrieb François Bissey:

Yes I would like to see it. I have looked at what fflas-ffpack does to detect
the stuff but I want a practical output for that case.

> On 6/08/2019, at 10:26 AM, Markus Wageringel <markus.w...@gmail.com> wrote:
>
> It would have been nice to have the config log from when you had the failure.
>
> Would you still like to have it? I could reproduce it I suppose.
>
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

config.log

François Bissey

unread,

Aug 6, 2019, 1:34:02 AM8/6/19

to sage-r...@googlegroups.com

I meant the config.log of fflas-ffpack not sage’s one.

> On 6/08/2019, at 5:31 PM, Markus Wageringel <markus.w...@gmail.com> wrote:
>
> <config.log>

Markus Wageringel

unread,

Aug 6, 2019, 1:49:38 AM8/6/19

to sage-release

Oh, my bad. Here it is.

config.log

François Bissey

unread,

Aug 6, 2019, 3:41:07 AM8/6/19

to sage-r...@googlegroups.com

Thanks, between that and the source code I know understand what is happening.
The configure script never checked that the flags are supported by the compiler.
Instead it runs some assembly code to identify the cpu ID and infer the capabilities
from that information. Actual code using the extensions in question is not tested,
and therefore, neither are the flags.

The test code has the following comment

/* find supported instruction set
return value:
0 = 80386 instruction set
1 or above = SSE (XMM) supported by CPU (not testing for O.S. support)
2 or above = SSE2
3 or above = SSE3
4 or above = Supplementary SSE3 (SSSE3)
5 or above = SSE4.1
6 or above = SSE4.2
7 or above = AVX supported by CPU and operating system
8 or above = AVX2
9 or above = AVX512F
10 or above = AVX512VL
11 or above = AVX512BW, AVX512DQ
*/

For your cpu, with gcc-4.8.5 the program returned 12.

Justin C. Walker

unread,

Aug 6, 2019, 4:54:16 PM8/6/19

to sage-r...@googlegroups.com

> On Aug 3, 2019, at 04:56 , Volker Braun <vbrau...@gmail.com> wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

Built without problems on three macOS systems: 10.11.6 (mid-2015 MBP, Quad-core i7), 10.13.6 (2017 iMac Pro, 18-core Xeon W), and 10.14.6 (2017 MBP, Quad-core Core i7).

Testing (‘ptestlong’):
- all tests passed on 10.11.6 and 10.14.6
- test failures in one file:
1 item had failures:
1 of 12 in sage.libs.singular.polynomial.singular_polynomial_call
[55 tests, 1 failure, 406.69 s]
----------------------------------------------------------------------
sage -t --long --warn-long 70.3 src/sage/libs/singular/polynomial.pyx # 1 doctest failed
----------------------------------------------------------------------

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
I'm beginning to like the cut of his jibberish.
-----------

Reply all

Reply to author

Forward