[cfe-dev] LLVM Dev meeting: Slides & Minutes from the Static Analyzer BoF

[Alex Bradbury via cfe-dev]

On 3 November 2015 at 09:24, David Chisnall via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> On 3 Nov 2015, at 06:37, Chris Lattner via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>> If you instead introducing a new IR that uses the Clang type system but somewhat lowered operations, you could significantly simplify CodeGen (which, of course, should also be named IRGen).  CILGen would handle things like lowering of temporaries, ctor/dtor invocations, control flow operations, etc.  The resulting “CIL” code would provide the natural representation for flow-sensitive clang warnings as well as the path sensitive ones that the static analyzer produces.  By having a first-class IR, we could entertain ideas of linking these files together to do interprocedural static analyses.
>>
>> That said, the huge and major disadvantage of this direction is that it is a tremendous amount of work to do...
>
> While I agree with everything Chris said, if someone is going to work on this please pick a name other than CIL: it is already used for a C source-to-source translation tool and would cause all manner of confusion to reuse it here.

And of course CIL, the bytecode target of .NET.

Alex