By: Michael S (already5chosen.delete@this.yahoo.com), May 18, 2022 5:36 am
Room: Moderated Discussions
anonymou5 (no.delete@this.spam.com) on May 18, 2022 5:06 am wrote:
> > > Stop coddling Intel. :)
> >
> > Poor advice and silly error message and failure mode for any software you intend for others to use.
> >
> > Coding a simple scalar reference is almost always a good
> > idea to test optimized implementation against and port
> > to other architectures, so you would have that code already
> > and it's simple to fall back to it on CPUs that don't
> > support a particular implementation. It might be quite a
> > bit more more than 2-3x slower than AVX512 but you can
> > still print a warning it's not optimized, the point is you
> > don't error out and send your users the message that
> > you are an incompetent clown who can't make working programs when everybody else manages to do so.
>
> If you have the luxury of spare resources, and the desire to spend them on catering to a
> by-ten-years-from-now obsolete AVX512-less CPU core, then sure, knock yourself out.
>
More likely, the opposite is going to happen in the next ten years: AVX512-less CPUs will rule the installed base and AVX512 will be, at best, HPC-only curiosity.
2021-2022 are peak years for AVx512 in terms of shipment and 2023 would be a peak year in terms of installed base.
> And if you insist on "incompetent clown" verbiage, then you should tack that label to the
> folks pumping out AVX512-less CPUs a decade from now, not resource-constrained coders.
>
> ;-)
> > > Stop coddling Intel. :)
> >
> > Poor advice and silly error message and failure mode for any software you intend for others to use.
> >
> > Coding a simple scalar reference is almost always a good
> > idea to test optimized implementation against and port
> > to other architectures, so you would have that code already
> > and it's simple to fall back to it on CPUs that don't
> > support a particular implementation. It might be quite a
> > bit more more than 2-3x slower than AVX512 but you can
> > still print a warning it's not optimized, the point is you
> > don't error out and send your users the message that
> > you are an incompetent clown who can't make working programs when everybody else manages to do so.
>
> If you have the luxury of spare resources, and the desire to spend them on catering to a
> by-ten-years-from-now obsolete AVX512-less CPU core, then sure, knock yourself out.
>
More likely, the opposite is going to happen in the next ten years: AVX512-less CPUs will rule the installed base and AVX512 will be, at best, HPC-only curiosity.
2021-2022 are peak years for AVx512 in terms of shipment and 2023 would be a peak year in terms of installed base.
> And if you insist on "incompetent clown" verbiage, then you should tack that label to the
> folks pumping out AVX512-less CPUs a decade from now, not resource-constrained coders.
>
> ;-)