VS2017 build errors jdk/jdk

[Alan Bateman]

On 10/05/2022 13:57, erik.joelsson at oracle.com wrote:
>
> Because of how much specific logic we need in configure for each 
> version of Visual Studio, we have generally kept configure support for 
> older versions of VS for a long time, to not unnecessarily limit 
> people. We removed 2015 and older when we moved to C++11 in Hotspot as 
> 2017 or later was a hard requirement.
>
> Which compiler versions actually work depends on if anyone wants to 
> keep up with the maintenance to keep them working. If VS2017 becomes 
> unusable and nobody wants or is able to fix it, then I agree that we 
> should remove support from configure.

I don't think the logic in the build is the main concern, instead it's 
requiring all changes to shared + windows code to be buildable with 
VS2017 is a tax. So hopefully support for this version can be dropped soon.

-Alan.