tree 549cc334d4e04c47b9152ae20e0d68a83d158bd7
parent 034d4dcad6396d1241e8262e69871b8d61da7e4f
author Daniel Paoliello <danpao@microsoft.com> 1776182207 -0700
committer GitHub <noreply@github.com> 1776182207 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJp3mO/CRC1aQ7uu5UhlAAAzaEQAIxaXBIWsSJF+GER0fNdAVyq
 ZZu8GZfu910QABphSt6XVf/mnG/q/6/FXuOMhWC/fCcZ/uNxGTztbKKwo+IKF8XJ
 gk1qDTIg/wQwm5DWNAjvRfL7YOoO8D2jMvQREk7pUlmASCeHXrxjnhq3T29osMvy
 Q5Rq5WnEYxACXDaf1RGXrQAl3f5dLEfsxRx9qNQVsLZjxrtXeIknpefJ5zZGEEA6
 KI/N7kMP8mGFiLIe5OF85urQZezP2Vgx9fFqjfJiHJmgNYZgHcJr0U44obtpOyAy
 GonEg5tmhrq7cHWlBJoTnoTQhTY2Kq6euReFQLvGlchGwhUwA9bTuHcKPYp10IKG
 Rs/B/PdDpVnuNWarysGdLeIh2qL6GkUdIL3Sxouidd4KF66yllERb5DWnTeS7/PX
 FxlWh5o/uDqEI12AiQFOwBG4zDHQy+WFT4J6BvK+IizP6BSahB4281o2OHmjjcty
 qVLhFIvZdYFNIx58tnY5hRAHw0zLEkr1ltJRUVS4qEUQmy7IYKRzfQsLkdwKK6NE
 V+cVfzWCZNlfDKkwS4tG6w2fkAFhDZA62zg0F13oQnVvraWHUZvPmQO1rwbsVC7r
 APwMklkfSACIozwYDNmVJY1ZC1EJCV144rQiqim1TwQBR9N9plzvqA/aGExsXkfZ
 R/x3GfvcEpkUH7hUZ6Vy
 =EGG4
 -----END PGP SIGNATURE-----
 

[win] Add a flag to control the Control Flow Guard mechanism on Windows (#176276)

Windows Control Flow Guard (CFG) has two different "mechanisms" or
"patterns":
* Dispatch: the caller calls into the CFG function, which both checks
the target callee and then calls it.
* Check: the caller calls the CFG function which only checks the target
callee and then must separately call the callee.

LLVM has followed MSVC's pattern for selecting the mechanism based on
the target architecture. These defaults in MSVC are based on tests for
performance: Dispatch produces a smaller code size, whereas Check is
more friendly to branch predictors.

It is possible, however, for a given workload, call pattern or target
CPU that someone may want to select a different mechanism to use for
their code.

This change adds a new Clang and CC1 flag to force a CFG mechanism:
`-fwin-cfg-mechanism`. This can be set to `automatic` (lets LLVM choose
a mechanism), `force-dispatch` or `force-check`.

Also adds the support for the equivalent MSVC flag
`/d2guardcfgdispatch`.

NOTE: Arm64EC only supports the check mechanism. It should be noted that
MSVC emits the "dispatch" name for the call checker (for legacy reasons)
but uses the check mechanism.