We have already heard requests for a move to C++20. The reason for not yet making this change is that C++20 support in Apple's clang is not yet complete so we are doing further research on this topic and would welcome further input on whether this is a major issue or not.
This might be a stupid question, but why not upgrade to glibc 2.34
(EL9) rather than glibc 2.28 (EL8)?
Developers not on MacOS (e.g., internal development at a Linux-based studio) don't care.
I'm much more concerned with the ABI change, I think that's going to be incredibly disruptive. Though also inevitable. I'm really not sure how to navigate that, since it will mean link-incompatibility with all the standard packages installed with the OS. I can only assume that this means everybody has to make a hard break away from CentOS 7 to be compatible with VFX Platform 2023, and I don't know how feasible that is. Have the big vendors already signalled that their releases next year will be using new ABI and some other Linux distro will be their standard for support?
On Mon, May 9, 2022 at 9:02 AM Larry Gritz <l...@larrygritz.com> wrote:Developers not on MacOS (e.g., internal development at a Linux-based studio) don't care.Fair, but software vendors of complex DCCs with a large MacOS customer base may care. If they do then they should let us know.
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAEg-Je8ge-ZP%3D_RPSYAPSSNk7oVnVWVmkMWq2N6eQQVF8PLQBQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAOOm49S4KZCfK-mXMJuf5RT1NPE%2BjsEcV7V5aee%3DC%2BXx1fS2VA%40mail.gmail.com.
Rob Fanner
Director of Engineering - Platform
Web: www.foundry.com
The Foundry Visionmongers Ltd. - Registered in England and Wales No: 4642027 - Address: 5 Golden Square, London, W1F 9HT - VAT No: 672742224
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/SYBP282MB3028CCDE1C1433AC270698F59CC99%40SYBP282MB3028.AUSP282.PROD.OUTLOOK.COM.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/c9937b0d-83f1-4d7a-855e-380594e043c9n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/c9937b0d-83f1-4d7a-855e-380594e043c9n%40googlegroups.com.
The Draft CY2023 VFX Reference Platform has been published at https://vfxplatform.com.
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CABiBYowY1c9pK_8UqED2vToHZmurH3p_xxuAUNPcP8kBFn%3DJyQ%40mail.gmail.com.
On Mon, May 9, 2022 at 11:24 AM Nick Cannon <nick....@gmail.com> wrote:The Draft CY2023 VFX Reference Platform has been published at https://vfxplatform.com.On the note to move to oneTBB for CY2024, I'd presume the plan is to also move to oneMKL for CY2024 as well?
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/d3ea6ebb4f4b4f3f832626a9d2efb6cd128ac1dc.camel%40marcomeyer-vfx.de.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAFj%3DrwOjemqQutLiJBmXfcWfK722p_TteOb90Qw2T%3Daa2-kiwQ%40mail.gmail.com.
One question, moving forward, will the VFX platform choose between Alma or Rocky or both will be part of the standard?
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CABiBYoymACJt3xUpQNrMP9wOJnY4hYoLnFOu0qAodeibsB8b8w%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CABiBYoyeotu35ww%3Ds9X3fT2jtr7Jby1t6KMA1PcxDKecAXs%2BVA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/071ecb69-70eb-4a9f-a891-5d00006d7ab4n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/071ecb69-70eb-4a9f-a891-5d00006d7ab4n%40googlegroups.com.
With the context of Mike's excellent letter here, I'd like to reiterate that I really believe CY2023 should upgrade to the EL9 base (glibc-2.34) rather than recommending the EL8 base (glibc-2.28). This does not preclude compatibility with existing DCC software that has been built for glibc-2.28, as newer platforms have backward compatibility.
On Jun 13, 2022, at 12:10 PM, Neal Gompa <ngom...@gmail.com> wrote:
The biggest advantage of glibc-2.34 is that hwcaps and hw accelerated
libraries based on CPU capabilities are available. This makes it
considerably easier to ship high performance libraries with graceful
fallbacks.
It's briefly mentioned in a blog post about RHEL 9 too:
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
I don't know if any studios still have older hardware but this would certainly be a consideration for RHEL 9. FWIW, and mind you this was 4 years ago, we were not able to upgrade our minimum requirements to SSE4.2 and had to go back down to SSE4.1 due to render farm machines of one particular large client.
- x86-64-v2 brings support (among other things) for vector instructions up to Streaming SIMD Extensions 4.2 (SSE4.2) and Supplemental Streaming SIMD Extensions 3 (SSSE3), the POPCNT instruction (useful for data analysis and bit-fiddling in some data structures), and CMPXCHG16B (a two-word compare-and-swap instruction useful for concurrent algorithms).
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAJZe6MAeNigheWn0dG6xpdLVrfOAP%3DKLrfpff%2BO8iHGWyLwqkQ%40mail.gmail.com.
Many (most?) software renderers implemented that requirement a while ago. Going through my emails it looks like Arnold did this in 2016, Vray 2018, Houdini/Mantra 2018, Renderman 2019, etc...
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAOOm49SGpvqTkFkDXoKUZ9ZBgMdWtUsQP5id%2B0HW%3Dqg0W2UCpA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CABiBYoxy9ivjtmtk_M8HjZnKa%2Bsv29PyPZtPb6Wfi9miDmxN%3Dw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAFj%3DrwNrNQ2Ym5wQqO9L5J9FW2GDL8cTva6CBLNiTUwxEVcj_g%40mail.gmail.com.