Open gilles-peskine-arm opened 7 months ago
After some internal discussion our preferred resolution would be to drop support for VS 2015 (and 2013) from Mbed TLS 3.6 onwards, i.e. in development
starting now. This is pending discussion on the mailing list.
Per the Visual Studio product lifecycle https://learn.microsoft.com/en-us/visualstudio/productinfo/vs-servicing#older-versions-of-visual-studio, VS 2013 and 2015 are currently on extended support, but their support will end during the lifetime of Mbed TLS 3.6 LTS. VS 2017 will expire around the same time as Mbed TLS 3.6.
At the time of writing, the
development
branch triggers an internal compiler error in Visual Studio 2015 when buildinglibrary/psa_crypto_ecp.c
. The problem started between fb133513d60e037c626e919e1ff76c2bc6446481 (pass) and 4d4891e18ac336d8c85e67828fdb2c582461f449 (fail) (diff).Log excerpt: