[llvm-dev] [GSoC'16] Weekly Status - Zhengyang Liu

Zhengyang Liu via llvm-dev llvm-dev at lists.llvm.org
Mon Jun 13 02:07:07 PDT 2016

I am sorry for this mess, could you please delete this mail, I have uploaded a new report.

Best regards,


From: Zhengyang Liu <zhengyang-liu at hotmail.com>
Sent: Monday, June 13, 2016 4:59 PM
To: llvm-dev at lists.llvm.org; svadev at lists.cs.illinois.edu
Subject: [svadev] [GSoC'16] Weekly Status - Zhengyang Liu

Dear llvm and sva community: This is to brief you the progress of SAFECode's Memory Policy Hardening, for those who are interested to see the detailed proposal please consider [1] , for those who are interested to see the my working repository please consider [2]. During the previous weeks I have improved the robustness of bbac implementation in SAFECode. I conclude the work done during this week as follows: Testing: 1. Fixed a bug in SpecializeCMSCalls. CFIChecks pass, which happens before SpecializeCMSCalls, produces a global variable called TargetList. The TargetList contains the targets of the specified function call and it includes the declarations of __loadcheck and __storecheck. The specialize functions in SpecializeCMSCalls use a cast which only accepts the callinst of __loadcheck and __storecheck, these users in the TargetList cause the crash. 2. Fixed a bug in ExactCheckOpt which will cause safecode crash if the target basic block has only one instruction. 3. Fixed a bug which caused the test failure of safecode/test/core/byval-001.c and byval-002.c. 4. Successfully generate the gzip and flex using safecode with bbac support. Currently it will produce some load/store error at runtime, I will check is that a true positive error this week. Plan for next week: 1. Discuss with my mentor Dr. John Criswell about the support of VLA size alloca. 2. Test the bbac implementation on other software and find if there is any bugs. Please provide any feedback/suggestion including for format of this email. I would also like to thanks my mentor John Criswell and other community members for providing quick help every time when I asked. Best regards, Zhengyang. [1]https://docs.google.com/document/d/1SNmdULUqN52zDhM1Odw93DW_vX-2WlL0VgceNWaMLP0/edit?usp=sharing<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1SNmdULUqN52zDhM1Odw93DW-5FvX-2D2WlL0VgceNWaMLP0_edit-3Fusp-3Dsharing&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=GcTcRqvnhx8CtEmraMrjtmJijhJOjAcP0OQX3AZCRIM&m=a1toL_hZ1MHTHVJwMBz1J64lK1Uer_kRZhVsruoPSyo&s=HdM8an5c2IgeWYi_wpBhlbkjzWu3wsDBIgBS2Cr0T7I&e=> [2] https://github.com/zhengyangl/safecode-llvm37/tree/safecode+llvm37<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zhengyangl_safecode-2Dllvm37_tree_safecode-26-2343-3Bllvm37&d=CwMGaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=GcTcRqvnhx8CtEmraMrjtmJijhJOjAcP0OQX3AZCRIM&m=a1toL_hZ1MHTHVJwMBz1J64lK1Uer_kRZhVsruoPSyo&s=ONXNUs0W3QXEcsiDnayzccrVqnBEwhv8Pu7ssmsPm9M&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160613/a8b30ac9/attachment.html>

More information about the llvm-dev mailing list