- User Since
- Jun 20 2019, 2:18 AM (71 w, 2 d)
Tue, Oct 13
Thanks @aeubanks! I don't yet have commit access and my colleague is on leave.
Mon, Oct 5
Ping @mehdi_amini - is this what you were asking for the CFGuard pass?
Always initialize loadThunkSym pointer.
Thanks for the diagnostics @aeubanks! Does this now resolve the issue with the Chrome build?
Sep 28 2020
Rewrite markSymbolsForRVATable() in terms of getSymbolsFromSections()
Sep 11 2020
Jun 24 2020
[CFGuard] Split into two passes and link into opt
Feb 25 2020
Feb 24 2020
Jan 10 2020
Jan 8 2020
- Address comments
- Make guard_nocf an attribute of individual call instructions
Jan 7 2020
Make guard_nocf an attribute of individual call instructions
Jan 3 2020
Nov 19 2019
Thanks for finding and fixing this @rnk! I've double-checked that Windows doesn't use AL for varargs (https://docs.microsoft.com/en-us/cpp/build/x64-calling-convention?view=vs-2019#varargs), but having a general mechanism for forwarding that doesn't assume a particular calling convention sounds like a good approach. This looks good from the control flow guard perspective.
Oct 23 2019
Split cfguard_setjmp test into target-specific tests and add missing cfguard_longjmp pass for ARM and AArch64.
Oct 21 2019
Formatting fixes for CFGuard patch.
Final changes and tests suggested by @rnk.
Oct 4 2019
Improved Control Flow Guard implementation.