This is a first step in the repo restructuring, see:
https://discourse.llvm.org/t/rfc-restructuring-of-the-mlir-repo/4927
Differential D121562
Move the IR and Interfaces library to a new mlir/core subdirectory (NFC) mehdi_amini on Mar 13 2022, 5:57 PM. Authored by
Details This is a first step in the repo restructuring, see: https://discourse.llvm.org/t/rfc-restructuring-of-the-mlir-repo/4927
Diff Detail
Event TimelineComment Actions The original proposal had: Parser/ Pass/ PDL/ Rewrite/ Support/ TableGen/ `` But I haven't checked if there has been new directories recently, I was planning to send reviews one directory at a time Comment Actions We need some coordination on the CMake include changes. Left some comments but also open to patching what you have and poking at it.
Comment Actions Could the RFC be updated with the final state planned here, intermediate steps that will be followed etc? Currently it is unclear from the RFC what state is (e.g., RFC seems unfinished/conversation just ended 27 days ago seemingly open ended), the end state unclear (as seen from review comments) and steps to get there unknown (e.g., is this just breaking changes in a row?). Judging each individually is convenient thanks. Test file locations is still a bit unclear too: seems like this is changing dir hierarchy but not affecting tests which is curious as I thought a goal was to have the association be easier, and for out of tree to be able to follow the structure closer.
Comment Actions Found the dependent https://reviews.llvm.org/D121568. With that, these CMake changes look good to me (at least to the level of unblocking the refactor -- I think we will want to come back and clean some things up when you are done). Comment Actions I'd prefer we resolve Jacques comments, and get a good understanding of what the final plan is before moving forward with anything (adding a block until then). Comment Actions By "final plan" here, I don't mean the perfect state of the world. I'm more interested in communicating with the community what is happening right now, and the path we will take moving forward (even if it's incremental). Comment Actions LGTM on the patch itself, but I think core/ should retain a lib/ directory. I don't see a huge cost in doing so, and it has a big benefit (IMO) of maintaining the separation between public/private API. Relaying the current plan to the community though is still very important to me here, and I think that should be done before we starting submitting patches. Comment Actions (agreed with River: my acceptance is of the cmake changes specifically, which look good and I think are big step forward for the project) |
Why wouldn't it be practical? I think if you add the generated binary include dir at the library level similar to how adding the source include, it should work (or it will once the AddLLVM.cmake changes in https://reviews.llvm.org/D120788 go in).