If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Should we expect no differences in performance of the generated binaries then?
Depends on timing relative to cleaning up work for upstreaming. There's usually a certain amount of "let's try this... hey that works.... now how the heck do we fit that into the upstream project patterns ?".
I don't think we have enough people working on the compiler to maintain an IP-safe but non-upstream tree yet, similar to what we recently started publishing for gfx drivers (amd-staging-4.9 / 4.11).
If it's worth enough, they'll probably find a way. It does seem a bit overly protective but who really benefits from compiler enhancements. Answer: everyone!
GCC could also use a little more love in the Zen department... the initial znver1 patches submitted almost 2 years ago use the cost model of carrizo/excavator, which
produces worse results than e.g. using the haswell cost model.
just a thought this zen ryzenmicroarchitecture must have brought a bunch of new instructions along with it. as far as i know these instructions can vary between manufacturers thinking of intel's vtx vs amds. will not gcc be updated to take benefits of these instructions while generating binaries for ryzen platform? did i get it right? pardon my lack of knowledge
And who on earth should enable a specific architecture flag despite Gentoo users? All the software out there is compiled more generically ...
Extra performance has its place ( video editing software, math heavy software, game engines, etc. ). GUI is not such software. Be sure most of the heavy software have different code paths for different processors ( even from the same vendor ), even for different cache size/hierarchies for that matter.
Huh ? The compiler teams have been submitting Ryzen support upstream into LLVM for quite a while now.
This is just a binary release with the standard binary EULA as far as I know.
Why would we try to push a binary upstream ?
Seemed like you guys were just taking clang, adding patches, and holding Zen optimization hostage in a proprietary compiler.
Good to know that's not what it is.
Comment