[llvm-dev] [RFC] Create llvm/lib/Frontend
Chris Lattner via llvm-dev
llvm-dev at lists.llvm.org
Thu Nov 28 15:30:03 PST 2019
> On Nov 25, 2019, at 10:36 AM, Doerfert, Johannes <jdoerfert at anl.gov> wrote:
>> What are the other things? Naming is often helped by having examples
>> from the broader pool that will shape this. It will also be helpful
>> to understand what would be “in” vs “out” of scope for this over time.
> One is toolchain handling, which should be available to the linker
> plugin so we can do fat binary linking without going through the clang
> There is a desire to share driver code in here as well, Peter and Mark
> can probably elaborate on that.
> I predict we find more use cases over time.
Got it - the thing is, each of these use cases will have different dependencies other implications. I think that splitting them into separate subdirectories under lib/Frontend/ is a good way to go.
>>>> WDYT about naming it something like "lib/OpenMPGen” and
>>>> generalizing/renaming it later when the scope is more clear?
>>> I can do that. It was also proposed to do "lib/Frontend/OpenMP" or
>>> something similar. Would that help or would you prefer not to have the
>>> top level "Frontend" until we actually move other things?
> So `lib/Frontend/OpenMP` for the OpenMP specific part seems to be a
> popular option. I'd like to go ahead with this soon, please let me know
> if there is disagreement. FWIW, it should be easy to rename/move the
> code later anyway.
More information about the llvm-dev