similar to: [GSoC'16] Proposal for Enhance SAFECode’s Baggy Bounds Checking

First of all, I am really sorry about my time scheduling. I did not manage to upload my proposal at the last minutes before Google Summer of Code submission deadline. Could you kindly take the following revision as my final proposal? Abstraction --------------------- This projects will enhance the ‘Baggy Bounds with Accurate Checking’ (BBAC) [1] work. By adding information to the memory object’s

Dear LLVM and SVA community: This is to brief you the progress of this week. I mainly focused on minor fixes this week. Following is what I finished this week. 1. Move the implementation of runOnModule of RegisterGlobalVar pass from .h back to .cpp file. 2. Introduce two new functions to register and unregister function prototypes on llvm.compiler.used. 3. Added two regression tests for

Hi, everyone This proposal covers the OpenProjects idea 'Port the Bigloo Scheme compiler, from Manuel Serrano at INRIA Sophia-Antipolis, to output LLVM bytecode.' There is not a popular functional language frontend yet on LLVM. To my knowledge, this is mostly because LLVM is lack of runtime support for the functional language needs, and C foreign function interface calls are relatively

John Criswell wrote: > If you're interested in SAFECode, the first step is to get SAFECode > working with a newer version of LLVM. A Master's student did some > work on this last summer with LLVM 3.7 but didn't finish. It would > now need to be updated to LLVM 3.8 (though I suppose a completed LLVM > 3.7 port would be fine with me). > > After that, there are

Dear Michael, If you're interested in SAFECode, the first step is to get SAFECode working with a newer version of LLVM. A Master's student did some work on this last summer with LLVM 3.7 but didn't finish. It would now need to be updated to LLVM 3.8 (though I suppose a completed LLVM 3.7 port would be fine with me). After that, there are some interesting projects on which to

Hi, everyone. I'm a senior at Swarthmore College and would love to work with LLVM this summer. I'm interested in systems languages and security, and I'll start a PhD on these topics this fall. I also do a good deal of open source development and auditing with OpenBSD and a variety of other projects. I spent last year's GSoC doing security auditing for Pidgin/libpurple. GSoC seems

Dear Community, As I keep you update with my progress by writing weekly report, this report is covering the information about how we are processing. For those who are interested in these weekly reports, please check [1]. In general, the progress of this project is in working order. Before the midterm, I have done the following works: 1. Finish the SAFECode llvm 3.7 portation. Currently it

Dear Josh, > If I understand correctly, if you find memory leak, you want to find the corresponding call(s) to malloc() that allocated the memory object, correct? Can you more completely explain what you are trying to accomplish? Thanks for your reply. In my task, I use data flow analysis to locate a program point where a malloc must be leaked (by must leaked, I mean (a) it must be

Greetings, Our telco called last week, saying that a lot of channels on our PRIs are blocked. And with blocked they have the following description in the Siemens exchanges: BBAC BLOCKED BACKWARD This status is set when the partner exchange has a blocking set and the signaling of the trunk (non-CCS7) is able to report this blocking in the backward direction. This status can

Dear LLVM developers: Here is my another proposal of LLVM. Any suggestion would be welcome! * ** * *** Integrate Baggy Bounds Checking into SAFECode*** * * *Abstract:** * Baggy Bounds Checking (BBC) is an efficient bounds checking technique that pad and align objects to powers of two and enable allocation bounds. It uses a contiguous array as bounds table to enable

Dear Sanjoy Das and community. I was tried to fix a bug in the pass InitAllocas from SAFECode. This is a function pass and will insert a prototype of 'llvm.memset.p0i8.i32' in the module at doInitialize() stage of the pass. But, this prototype will be eliminated by strip unused function optimization since there is no call on this function after doInitialization(). Therefore there will be

Hi I have an asterisk box with digium hardware connected to a Siemens EWSD version 15 using a crossed E1 cable. The asterisk is serving as a h323 media gateway. When i start asterisk, the Siemens gives me this alarm: REPORTES GENERADOS EN LA EWSD AES/V15SBOL/BOLCBK1V51327079/013 05-06-06 11:25:38 7773 3062/03728 HF.ARCHIVE-80040

Dear John, > When you say "must be allocated," you mean it must have been allocated via a call to a heap allocator (e.g., malloc(), calloc(), etc), correct? Yes, I mean heap allocators. In fact, I'm implementing the idea of the ICSE 2015 paper Safe Memory-Leak Fixing for C Programs. > Also, are you performing intra-procedural or inter-procedural data-flow analysis?

Dear LLVM community. I have a function pass. This pass will insert a llvm intrinsic function prototype (llvm.memset.p0i8.i32) to the module at the doInitialize stage. Then at runOnFunction Stage, this pass will find the insert points and insert calls of this intrinsic function. However, when the -O2 flag is turned on, the strip unused function optimization will automatically delete this

Hi Zhengyang, Do you mind sharing _why_ you need the intrinsic declarations to stay around? It is possible that there is a better way of solving your problem. Thanks! -- Sanjoy

Hi Adam, On Wed, Mar 23, 2016 at 1:50 PM, Adam Nemet via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On Mar 22, 2016, at 5:13 PM, Philip Reames <listmail at philipreames.com> > wrote: > > > > On 03/20/2016 05:38 AM, Aries Gunawan via llvm-dev wrote: > > > *Loop Dependence Analysis Infrastructure. *I have looked in the source > codes repo and I

> On Mar 22, 2016, at 5:13 PM, Philip Reames <listmail at philipreames.com <mailto:listmail at philipreames.com>> wrote: > > > > On 03/20/2016 05:38 AM, Aries Gunawan via llvm-dev wrote: >> Hi everyone, >> >> I am very interested in contributing to LLVM project in this year’s GSoC. I am new with LLVM, but this is used in the compiler course in my

On 03/20/2016 05:38 AM, Aries Gunawan via llvm-dev wrote: > > Hi everyone, > > I am very interested in contributing to LLVM project in this year’s > GSoC. I am new with LLVM, but this is used in the compiler course in > my university. So, I am thinking to involve in LLVM development to > have a better knowledge of the system. Currently, I am preparing the > proposal.

Ok, makes sense. My suggestion is that we patch the IR Verifier to ensure that the mask is indeed a vector of constants and/or undefs. Right now it only runs the standard checks for instructions. We will also run Alive2 on the test suite to make sure undef is never replaced in practice. Thanks, Nuno -----Original Message----- From: Eli Friedman <efriedma at quicinc.com> Sent: 27 de

Hi everyone, I am very interested in contributing to LLVM project in this year's GSoC. I am new with LLVM, but this is used in the compiler course in my university. So, I am thinking to involve in LLVM development to have a better knowledge of the system. Currently, I am preparing the proposal. One of the project that caught my eyes is "New Transformations and Analysis". Several