mgrid also on IA64: https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-terbium-head-64/recent.html

Can't reproduce mgrid, facerec and apsi regression on a Haswell machine.

mgrid also on AMD Fam10: https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-megrez-head-64/recent.html

(In reply to Richard Biener from comment #3)
> mgrid also on AMD Fam10:
> https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-megrez-head-64/recent.html

Interesting about this regression is that mgrid is a single source benchmark. Thus I would not expect a difference in between LTO and non-LTO mode.

I can confirm regression from 517 -> 537s of gamess on a zen2 machine with -Ofast -march=native. Let me bisect this one.

Thanks! -flto makes differnce even for single file benchmarks (because of thrown away type info and extra info from linker). So perhaps that is reason why it did not reproduce?

(In reply to Martin Liška from comment #5)
> I can confirm regression from 517 -> 537s of gamess on a zen2 machine with
> -Ofast -march=native. Let me bisect this one.

It's caused by r256644.

Reading the log, it gamess regression at 14th should not be gather/scatter because it reproduces on zen2 where we disable them.

About the 19th regression, it would be nice to also bisect it (hopefully it will reproduce with -flto as discussed earlier). The reason is that it reproduces at ia64 even with profile feedback
https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-terbium-head-64-FDO/recent.html
which seems to disprove the likely suspect that it is a result of predictor changes from that day (mostly disproves: predictors still do affect FDO path but it is unlikely they affect it importantly unless there is other bug)

MCF regression of spec2017 is due to predictor change.

Author: rguenth
Date: Fri Feb 16 13:47:25 2018
New Revision: 257734

URL: https://gcc.gnu.org/viewcvs?rev=257734&root=gcc&view=rev
Log:
2018-02-16  Richard Biener  <rguenther@suse.de>

	PR tree-optimization/84037
	PR tree-optimization/84016
	PR target/82862
	* config/i386/i386.c (ix86_builtin_vectorization_cost):
	Adjust vec_construct for the fact we need additional higher latency
	128bit inserts for AVX256 and AVX512 vector builds.
	(ix86_add_stmt_cost): Scale vector construction cost for
	elementwise loads.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/i386/i386.c

The gamess regression mentioned should be fixed.

I can confirm that gamess is fixed. In addition tonto's regression from earlier cost tuning was fixed as well. There is nice improvement to galgel (15400->15800) which is not fixing earlier regression and apsi (4580->4680)

Zhere is small regression on zeusmp (39.6->39). Apsi is not on best score so far.
There is also a noticeable code size reduction.
So it looks really good!

From spec2000 we stll have mgrid, facerec and fma3d. facerec is related to code size as it went up and down 19% during inliner tuning. It is not up with final values and may be worth to investigate it.

tfft of polyhedron is aslso still regressing. Martin, perhaps you can bisect that one as it seems most consistent?

Honza

> 
> tfft of polyhedron is aslso still regressing. Martin, perhaps you can bisect
> that one as it seems most consistent?
> 

Can't see any difference for both tfft and tfft2 benchmarks on my Haswell machine. Can you reproduce that locally?

Honza can you reproduce that or can we close it?

(In reply to Richard Biener from comment #3)
> mgrid also on AMD Fam10:
> https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-megrez-head-64/recent.html

re-bounded, possibly with the fix for PR85455.  The IA64 tester didn't re-bound.

Note this PR is a mess with mangling many regressions into one bug...

GCC 8.1 has been released.

GCC 8.2 has been released.

Richi, Honza: Do we want to then close it?

GCC 8.3 has been released.

I'm simply closing this bug now.  Please always use _separate_ bugreports for different benchmarks.