RFR: 8307160: [REDO] Enable the permissive- flag on the Microsoft Visual C compiler [v3]

Phil Race prr at openjdk.org
Mon Aug 14 21:00:14 UTC 2023


On Thu, 10 Aug 2023 04:04:58 GMT, Julian Waters <jwaters at openjdk.org> wrote:

>> We should set the -permissive- flag for the Microsoft Visual C compiler, as was requested by the now backed out [JDK-8241499](https://bugs.openjdk.org/browse/JDK-8241499). It can be done with some effort, given that the significantly stricter gcc can now compile an experimental Windows JDK as of 2023, and will serve to significantly cut down on monstrosities in ancient Windows code
>
> Julian Waters has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Remove negation in os_windows.cpp

I have no time to look at the client changes for quite some time so do not push it. No matter how many other people approve it.
And in the meantime you can 
(1) explain how many client tests you ran - and it had better be all of them :-)
(2) add a comment in the PR to explain each client change you made - at the site of the change.
  Comments like "Fields in awt_TextComponent.cpp" are not an explanation
(3) On the broader front, I note that you just start off with "We should set the -permissive- flag for the Microsoft Visual C compiler"
without explaining WHY and what it does. In fact from what I've read about -it seems like we would not want it .. it downgrades errors to warnings .. and surely that's a bad thing ?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/15096#issuecomment-1678049894


More information about the security-dev mailing list