A patch to move codegen includes into public include

Rafael EspĂ­ndola rafael.espindola at gmail.com
Mon Aug 25 08:11:27 PDT 2014


I can see why you need some of codegen exposed, but do you really need
all of it? Maybe we should have a lib/ABI that is used by lib/CodeGen?

On 23 August 2014 17:06, DeadMG <wolfeinstein at gmail.com> wrote:
> Dear all,
>
> I have attached a quick patch, which simply moves some previously-internal
> CodeGen headers into the public include, based on r216273.
>
> Placing these headers in the public include will drastically simplify the
> development cycle for the layer on top of CodeGen that I discussed on
> cfe-dev, targetted for 3.6. Developing that layer on top of 3.4 was a pain
> for me as requiring all my users and developers to build LLVM and Clang from
> source was time-consuming and fiddly.
>
> Ideally, this would be merged into 3.5 (although I believe that ship has
> sailed even for such simple patches) or a hypothetical 3.5.1. As this only
> moves a few headers from one location to another, extensive testing
> shouldn't be required, but just for the record, I tested on Ubuntu 14.04
> with no additional failures.
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>



More information about the cfe-commits mailing list