This is the mail archive of the
mailing list for the GCC project.
Re: [llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work
- From: Chris Lattner <clattner at nondot dot org>
- To: Leslie Zhai <lesliezhai at llvm dot org dot cn>
- Cc: llvm-dev at lists dot llvm dot org, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 6 Sep 2017 21:10:02 -0700
- Subject: Re: [llvm-dev] DragonEgg for GCC v8.x and LLVM v6.x is just able to work
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <59ae1670.4198630a.62679.139fSMTPIN_ADDED_BROKEN@mx.google.com>
> On Sep 4, 2017, at 8:13 PM, Leslie Zhai via llvm-dev <firstname.lastname@example.org> wrote:
> Hi LLVM and GCC developers,
> LLVM China http://www.llvm.org.cn forked DragonEgg https://github.com/LLVM-China/dragonegg because:
> * Some subprojects are impractical or uninteresting to relicense (e.g. llvm-gcc and dragonegg). These will be split off from the LLVM project (e.g. to separate Github projects), allowing interested people to continue their development elsewhere. http://lists.llvm.org/pipermail/llvm-dev/2017-August/116266.html
> * There are a lot of issues https://github.com/xiangzhai/dragonegg/issues so I need smarter developers' help.
Out of curiosity, what is motivating this work? What is the usecase for dragonegg these days, now that Clang has great C++ support? Are you interested in Ada + LLVM or some other frontend?