Re: [sage-devel] Compile sage with `-march=native` as a default

Thanks for your replies. I wasn't aware of `CFLAGS` and it works great. I think it makes sense to enable the SIMD-instructions with #27103 no matter if all of sage is compiled with `-march=native` by default. All it really takes to get the intrinsics wor

Re: [sage-devel] Compile sage with `-march=native` as a default

On 10/22/19 7:41 AM, Dima Pasechnik wrote: >> >> Set CFLAGS="-march=native" in your shell before running "make", and then >> pray that the sage packages respect that variable. > > many packages would ignore it, and C++ and Fortran modules won't be > affected by this, either. Well there's also CXX

Re: [sage-devel] Compile sage with `-march=native` as a default

On Tue, Oct 22, 2019 at 12:34 PM Michael Orlitzky wrote: > > On 10/22/19 7:00 AM, 'Jonathan Kliem' via sage-devel wrote: > > I was wondering, if it was possible to compile sage (or parts of it) > > with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). > > Some time ago I cre

Re: [sage-devel] Compile sage with `-march=native` as a default

On 10/22/19 7:00 AM, 'Jonathan Kliem' via sage-devel wrote: > I was wondering, if it was possible to compile sage (or parts of it) > with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). > Some time ago I created #27122 > for this. Se

[sage-devel] Compile sage with `-march=native` as a default

I was wondering, if it was possible to compile sage (or parts of it) with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). Some time ago I created #27122 for this. Why do I care about it? (I was told that many parts of sage could p