Re: Compilation flags in libgfortran

2013-10-19 Thread Igor Zamyatin
Yeah, I can try to do benchmarking with such optset instead of O3. Thanks, Igor On Thu, Oct 17, 2013 at 2:19 PM, Richard Biener wrote: > On Wed, Oct 16, 2013 at 12:22 PM, Kyrill Tkachov > wrote: >> On 16/10/13 10:37, pins...@gmail.com wrote: On Oct 15, 2013, at 6:58 AM, Igor Zamyatin

Re: Compilation flags in libgfortran

2013-10-17 Thread Richard Biener
On Wed, Oct 16, 2013 at 12:22 PM, Kyrill Tkachov wrote: > On 16/10/13 10:37, pins...@gmail.com wrote: >>> >>> On Oct 15, 2013, at 6:58 AM, Igor Zamyatin wrote: >>> Hi All! >>> >>> Is there any particular reason that matmul* modules from libgfortran >>> are compiled with -O2 -ftree-vectorize? >>>

Re: Compilation flags in libgfortran

2013-10-16 Thread Igor Zamyatin
Yeah, this is my point exactly. Atom case seems just triggered that fact. On Wed, Oct 16, 2013 at 2:22 PM, Kyrill Tkachov wrote: > On 16/10/13 10:37, pins...@gmail.com wrote: >>> >>> On Oct 15, 2013, at 6:58 AM, Igor Zamyatin wrote: >>> Hi All! >>> >>> Is there any particular reason that matmul

Re: Compilation flags in libgfortran

2013-10-16 Thread Kyrill Tkachov
On 16/10/13 10:37, pins...@gmail.com wrote: On Oct 15, 2013, at 6:58 AM, Igor Zamyatin wrote: Hi All! Is there any particular reason that matmul* modules from libgfortran are compiled with -O2 -ftree-vectorize? I see some regressions on Atom processor after r202980 (http://gcc.gnu.org/ml/gcc-c

Re: Compilation flags in libgfortran

2013-10-16 Thread pinskia
> On Oct 15, 2013, at 6:58 AM, Igor Zamyatin wrote: > > Hi All! > > Is there any particular reason that matmul* modules from libgfortran > are compiled with -O2 -ftree-vectorize? > > I see some regressions on Atom processor after r202980 > (http://gcc.gnu.org/ml/gcc-cvs/2013-09/msg00846.html)

Re: Compilation flags in libgfortran

2013-10-16 Thread Igor Zamyatin
Thanks a lot for the explanation! I can take care of the benchmarking but only on Intel hardware... Do you think that possble changes according those results would be acceptable? Thanks, Igor On Tue, Oct 15, 2013 at 11:46 PM, Janne Blomqvist wrote: > On Tue, Oct 15, 2013 at 4:58 PM, Igor Zamyat

Re: Compilation flags in libgfortran

2013-10-15 Thread Janne Blomqvist
On Tue, Oct 15, 2013 at 4:58 PM, Igor Zamyatin wrote: > Hi All! > > Is there any particular reason that matmul* modules from libgfortran > are compiled with -O2 -ftree-vectorize? Yes, testing showed that it improved performance compared to the default options. See the thread starting at http://g

Re: Compilation flags in libgfortran

2013-10-15 Thread Toon Moene
On 10/15/2013 03:58 PM, Igor Zamyatin wrote: Hi All! Is there any particular reason that matmul* modules from libgfortran are compiled with -O2 -ftree-vectorize? I see some regressions on Atom processor after r202980 (http://gcc.gnu.org/ml/gcc-cvs/2013-09/msg00846.html) Why not just use O3 fo

Compilation flags in libgfortran

2013-10-15 Thread Igor Zamyatin
Hi All! Is there any particular reason that matmul* modules from libgfortran are compiled with -O2 -ftree-vectorize? I see some regressions on Atom processor after r202980 (http://gcc.gnu.org/ml/gcc-cvs/2013-09/msg00846.html) Why not just use O3 for those modules? Thanks, Igor