Christoph,
Thank you very much for all the information you provided - the paper
"Estimating the
Impact of Scalable Pointer Analysis on Optimization" seems to be a good
reference also for
GOLF.
I am new to pointer aliasing and fancier techniques in CIL such as
symbolic
execution,
Alex,
On Fri, Sep 20, 2013 at 09:12:50AM +0300, Alex Susu wrote:
> The partial modules is very interesting. Was it used for a publication?
> If so, could
> you please tell me some reference(s).
The partial feature was written by the
original CIL crew Necula, McPeak, Weimer. It
look
Hi, Christoph,
The partial modules is very interesting. Was it used for a publication? If
so, could
you please tell me some reference(s).
If I see well partial does not use the deadcodeelim module, but, as
written in
CIL.pdf, it does if-statement simplification which goes in that d
Gabriel -
On Wed, Sep 18, 2013 at 08:41:04AM +0100, Gabriel Kerneis wrote:
> Do you know why Golf is not enabled by default?
No, I don't. Could be the dreaded
backwards-compatability whatever, though.
I don't see any reason not to hard-code `Golf'.
It never produced any false positives
Christoph,
On Wed, Sep 18, 2013 at 09:33:21AM +0200, Christoph Spiel wrote:
> (3) Precise pointer analysis turned out to be
> crucial. The default `Olf' module is much
> to imprecise, but you can simply replace it
> with `Golf' at the top of "ptranal.ml".
> Golf returns _much_ sma
Alex -
On Tue, Sep 17, 2013 at 04:21:43PM +0300, Alex Susu wrote:
> Did anybody use Dead code elimination (DCE)?
We used it, but that dates back almost a
decade, when we analyzed several large projects
in embedded environments.
Let me summarize the problems I still remember.
(1) CI
