search for: elkhound

...atics and I would want to build a start  up to  manufacture mobile phones ( OEM level ). I am currently in discussion with investors. We would want to use LLVM as our main compiler but we will need to complete it to have a "commercial grade" one. Here are our goals : -Use a modified Elkhound as C/C++ front-end : http://www.cs.berkeley.edu/~smcpeak/elkhound/ -Complete the ARM back-end -Fix the bugs to be able to compile a complete Cross Linux from scratch for arm with uclibc-nptl. http://trac.cross-lfs.org/milestone/CLFS 3.0.0 We believe that we will be able to speak of LLVM 2...

Hello, I would want to know what are the main differences between LLVM and C--. We need a robust compiler ( or at least the most promising to work on it ) with these features : -A GLR parser (use a modified Elkhound as C/C++ front-end):   http://www.cs.berkeley.edu/~smcpeak/elkhound/ -Complete the ARM back-end -To be able to compile a complete Cross Linux from scratch for arm with uclibc-nptl. http://trac.cross-lfs.org/milestone/CLFS 3.0.0 I look forward to your answer, Best Regards, Guillaume PS :...

...ne Error: Argument 'machine-licm' defined more than once! It seems like the constructor for this argument is being run twice. ellsif works as expected, but I'd like to figure out what's going wrong. The link command is: g++ -o ellsif ellsif.o elsa.o -g -Wall ../elsa/libelsa.a ../elkhound/libelkhound.a ../ast/libast.a ../smbase/libsmbase.a -L/home/rich/llvm-install/lib -lpthread -ldl -lm -lelf -lLLVMLinker -lLLVMArchive -lLLVMipo -lLLVMInstrumentation -lLLVMBitWriter -lLLVMBitReader /home/rich/llvm-install/lib/LLVMMSIL.o /home/rich/llvm-install/lib/LLVMCBackend.o /home/rich/l...

>Neither C-- nor LLVM provide this.  Why do you need a GLR parser >specifically? http://www.cs.berkeley.edu/~smcpeak/elkhound/ Parsing with arbitrary context-free grammars has two key advantages: (1) unbounded lookahead, and (2) support for ambiguous grammars. Unbounded lookahead is achieved by allowing multiple potential parses to coexist for as long as necessary. Similarly, ambiguity is handled by letting potential...

...his won't be able to handle a lot of interesting > cases. C++ requires a significant amount of semantic analysis just to get > parsing correct. You could surely save a lot of time reinventing the wheel by reusing an existing C++ parser, like Elsa: http://www.cs.berkeley.edu/~smcpeak/elkhound/ There are even OCaml bindings: http://www.cs.ru.nl/~tews/olmar/ These libraries were discussed on the OCaml mailing list recently: http://groups.google.com/group/fa.caml/msg/dd7dad5533647220 -- Dr Jon D Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/products/?e

On Wed, 19 Mar 2008, Argiris Kirtzidis wrote: > I'd like to hear your opinions and ideas for a proposal to improve > support for C++ parsing for LLVM's clang front end. Some meta feedback: C++ support in clang is a huge project, far and away more than any mortal can get done in a summer. While it would be possible to sketch out the parser itself in the summer (providing the

Hi all, I'd like to hear your opinions and ideas for a proposal to improve support for C++ parsing for LLVM's clang front end. Goal: Improve clang's C++ support. The scope of the project will be limited to C++ parsing, not code generation (I think the timeframe of a GSoC project and the complexity of C++ doesn't allow full C++ support to be developed). C++ parsing support