svadev AT lists.siebelschool.illinois.edu
Subject: Svadev mailing list
List archive
- From: Vassil Vassilev <vvasilev AT cern.ch>
- To: Baozeng <sploving1 AT gmail.com>
- Cc: "svadev AT cs.uiuc.edu" <svadev AT cs.uiuc.edu>
- Subject: Re: [svadev] memory safety for Cling
- Date: Mon, 22 Apr 2013 16:43:04 +0200
- List-archive: <http://lists.cs.uiuc.edu/pipermail/svadev/>
- List-id: <svadev.cs.uiuc.edu>
Hi,
On 4/22/13 4:12 PM, Baozeng wrote: Just out of curiosity, does Cling follow LLVM trunk, or does it stick with a particular LLVM release for awhile like SAFECode does? I have no idea. Maybe the cling developer Vassil could answer
you this question.
In the past we updated to LLVM and Clang's trunks on daily basis.
This is the most preferable way to do it IMO. However, recently we
started integrating cling in a bigger project at CERN and the amount
of time we were waiting for reviews was too long for us. Independent
on that we wanted to try enhancing the C++ Module support. This
required many non-trivial patches. Currently we are pretty close to
finishing the work in our branch and we will start feeding back the
patches in the mainline and I hope soon we will be back to at least
weekly syncs. Vassil |
- [svadev] memory safety for Cling, Baozeng, 04/17/2013
- Re: [svadev] memory safety for Cling, John Criswell, 04/18/2013
- Re: [svadev] memory safety for Cling, Baozeng, 04/22/2013
- Re: [svadev] memory safety for Cling, John Criswell, 04/22/2013
- Re: [svadev] memory safety for Cling, Vassil Vassilev, 04/22/2013
- Re: [svadev] memory safety for Cling, Baozeng, 04/22/2013
- Re: [svadev] memory safety for Cling, John Criswell, 04/18/2013
Archive powered by MHonArc 2.6.16.