llvm dev - Sep 2017 - DragonEgg for GCC v8.x and LLVM v6.x is just able to work

> On Sep 4, 2017, at 8:13 PM, Leslie Zhai via llvm-dev <llvm-dev at
lists.llvm.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.
Hi Leslie,

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?

-Chris

Dear Chris,

Thanks for your kind response!

The motivating of this work:

1. Clang can not build Linux https://bugs.llvm.org/show_bug.cgi?id=22830 
and LLVMLinux patch was not be maintained? 
http://llvm.linuxfoundation.org/index.php/Main_Page

2. Clang analyzer Frontend can not static analysis glibc or Linux 
https://bugs.llvm.org/show_bug.cgi?id=31017 but analyzer checker is able 
to find the bugs for KDE :) 
http://www.leetcode.cn/2016/11/analyzing-code-for-kde-qt-open-source-components.html

3. For leaning GCC plugin, GIMPLE, LLVM IR, GCC PASS, LLVM PASS, 
CodeGen, etc. from llvm-gcc and dragonegg, thanks for your great job!

The usecase for dragonegg:

1. mips64-linux-gnu-gcc (WIP), arm-linux-gnu-gcc and x86 GCC Frontend -> 
GIMPLE -> LLVM IR -> Assembly or for KLEE

2. GCC Frontend -> GIMPLE -> Clang AST (WIP)

I am interested in some other frontend, such as flang-clang 
https://github.com/flang-compiler/clang/pull/28 and it is glad to learn 
from other developers :) https://gcc.gnu.org/ml/gcc/2017-09/msg00022.html


在 2017年09月07日 12:10, Chris Lattner 写道:
>> On Sep 4, 2017, at 8:13 PM, Leslie Zhai via llvm-dev <llvm-dev at
lists.llvm.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.
> Hi Leslie,
>
> 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?
>
> -Chris
>
>
-- 
Regards,
Leslie Zhai - https://reviews.llvm.org/p/xiangzhai/