Herman Venter - The Common Compiler Infrastruture goes Open Source
- Posted: Apr 15, 2009 at 3:49PM
- 7 comments
Herman Venter announces the Common Compiler Infrastructure (CCI) as an
open source project
on codeplex! CCI is a set of tools and components that are useful to build compilers: readers and writers for MSIL and symbol files, and more.
You’ve may have heard and probably used different incarnations of CCI in the past: the FxCop introspection engine,
ILMerge,
Spec# or Code
Contracts are using CCI in many ways. Now, you can use it too: just sync the sources, build it, tweak it, etc… It’s all there on
codeplex at
Enjoy!
ps: Sorry for the low quality of the sound, my new microphone is on it's way...
The Research in Software Engineering team (RiSE) coordinates Microsoft's research in Software Engineering in Redmond, USA.
Comments closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.
More entries in this blog
-
Ben Livshits and Ben Zorn - Heap Spraying Attack…
-
Herman Venter - The Common Compiler Infrastruture…
-
Manuel Fahndrich and Peli de Halleux - The Synergy…
Follow the discussion
Oops, something didn't work.
What does this mean?
Subscriptions allow us send you email notifications when new content is added. You need to be signed in to Channel 9 to use this feature.What does this mean?
Subscriptions allow us send you email notifications when new content is added.sign up for email notifications?
What's the difference between CCI and Phoenix SDK ? (It was also a compiler/runtime tool optimizer)
I thought he was going to show all the herms he invented.
Indeed. We have some great content from Lang .NET that will air in a few weeks.
C
Phoenix and CCI certainly have areas of overlap and it is not always easy to decide when to use which.
I view Phoenix as a large and somewhat complicated tool kit that is primarily concerned with compiling unmanaged C/C++ to optimal machine code. Everything else is secondary and this has an impact on the usability of Phoenix for compiler front-end scenarios and simple MSIL production and consumption.
Use Phoenix when you are a Rocket Scientist and need to leverage the extensive support for control flow graphs, SSA and so on.
Remove this comment
Remove this thread
Close