On Mon, Sep 26, 2016 at 1:50 PM, leif <not.rea...@online.de> wrote: > Jean-Pierre Flori wrote: > > > > > > On Monday, September 26, 2016 at 11:47:00 AM UTC+2, Jonathan Bober wrote: > > > > On Mon, Sep 26, 2016 at 9:44 AM, Dima Pasechnik <dim...@gmail.com > > <javascript:>> wrote: > > > > > > > > On Monday, September 26, 2016 at 2:22:51 AM UTC, Jonathan Bober > > wrote: > > > > I recompiled with gcc 6.1.0, and get the same segfault. I > > did a ./sage -i gdb to get a better crash report, which is > > attached. I don't know if it is useful. Also, it mentions > > some gcc 5.1.0 paths, which seems odd. I don't know if that > > indicates that something is broken on my end. > > If in doubt, try building with '-mno-xop' in CFLAGS. AFAICT, *every* > GCC version supporting Bulldozer+ is broken w.r.t. mixing AVX and XOP > instructions (at higher optimization levels). (I haven't tried 6.x yet > though IIRC; GMP-ECM 6.4 built with '-march=native -O3' was an example > exposing this in the past, 7.x no longer does.) > > I can just set the CFLAGS variable, and Sage will use it (or add to it)?
Meanwhile, rebuilding produced the error again. By rebuilding from scratch, I really mean the following set of commands (which has some output and irrelevant commands omitted, but is otherwise an actual log of what I typed in, and not just a reproduction from my faulty memory). jb12407@lmfdb5:~/tmp$ rm -rf sage jb12407@lmfdb5:~/tmp$ git clone g...@github.com:sagemath/sage.git jb12407@lmfdb5:~/tmp$ cd sage jb12407@lmfdb5:~/tmp/sage$ gcc -v Using built-in specs. COLLECT_GCC=/opt/gcc-6.1.0/bin/gcc COLLECT_LTO_WRAPPER=/opt/gcc-6.1.0/libexec/gcc/x86_64-pc-linux-gnu/6.1.0/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../source-links/configure --prefix=/opt/gcc-6.1.0 --enable-languages=c,c++,fortran Thread model: posix gcc version 6.1.0 (GCC) jb12407@lmfdb5:~/tmp/sage$ git checkout develop jb12407@lmfdb5:~/tmp/sage$ export MAKE='make -j40' jb12407@lmfdb5:~/tmp/sage$ unset SAGE_ATLAS_LIB jb12407@lmfdb5:~/tmp/sage$ make (This terminates in an error building the documentation because of memory overcommit issues, but it builds everything else fine. That's a nice side effect if the overcommit problems, IMHO ;) Finally... jb12407@lmfdb5:~/tmp/sage$ ./sage ┌────────────────────────────────────────────────────────────────────┐ │ SageMath version 7.4.beta6, Release Date: 2016-09-24 │ │ Type "notebook()" for the browser-based notebook interface. │ │ Type "help()" for help. │ └────────────────────────────────────────────────────────────────────┘ ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Warning: this is a prerelease version, and it may be unstable. ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ This looks like the first time you are running Sage. Updating various hardcoded paths... (Please wait at most a few minutes.) DO NOT INTERRUPT THIS. Done updating paths. sage: m = random_matrix(RDF,500) sage: e = m.eigenvalues() BOOM! -- 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.
