similar to: [LLVMdev] Simplifying a front-end project

John McCall schrieb: > Vikram S. Adve wrote: >> For the translator in step (2), I've so far had them generate LLVM IR >> in memory using the LLVM APIs. They find it a *lot* of work to learn >> the LLVM APIs, which doesn't teach them much about compiler concepts >> per se. To simplify this project, I am considering changing the >> project so they

On Tue, Aug 25, 2009 at 3:01 PM, Vikram S. Adve<vadve at cs.uiuc.edu> wrote: > For my introductory Compiler Construction class, I have been giving > the students a project to write a simple compiler for a toy, single- > inheritance object-oriented language.  We give them a set of classes > implementing an AST for the language and a type checker as well.  The > students write

Vikram S. Adve wrote: > For the translator in step (2), I've so far had them generate LLVM IR > in memory using the LLVM APIs. They find it a *lot* of work to learn > the LLVM APIs, which doesn't teach them much about compiler concepts > per se. To simplify this project, I am considering changing the > project so they "print out" LLVM assembly directly

For my introductory Compiler Construction class, I have been giving the students a project to write a simple compiler for a toy, single- inheritance object-oriented language. We give them a set of classes implementing an AST for the language and a type checker as well. The students write (1) a scanner and parser to build the AST; (2) a translator from AST to LLVM; and (3) a couple of

On Wednesday 19 March 2008 21:27:18 Chris Lattner wrote: > 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

On 3/19/08, Argiris Kirtzidis <akyrtzi at gmail.com> 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. > > 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

Thanks for your feedback Chris, Chris Lattner wrote: > If I were going to pick, I would suggest focusing on getting simple > methods implemented, along with instance variables, etc through > -fsyntax-only. This should be a reasonable amount of work for a summer. > Something like this should work for example: > > class foo { > int X; > typedef float Z; > int

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

On Nov 24, 2009, at 8:30 AM, David Greene wrote: > On Monday 23 November 2009 09:01, Anton Korobeynikov wrote: >> Hello >> >>> It is a RISC with around 60 instructions like a 80c51 instruction set >>> (without mul/div) and with Direct or indirect memory acces. >> >> My estimate is something like a man-week for a person, who knows what to do >>

On 02/16/2017 12:08 PM, Stephen Canon wrote: >> On Feb 16, 2017, at 9:12 AM, Bagel <bagel99 at gmail.com >> <mailto:bagel99 at gmail.com>> wrote: >> >> I figured that the optimization of this would bedifficult (else it would >> have already been done :-)) > > Don’t make this assumption. There’s lots of opportunities for optimization > scattered

Pardon the length of this reply, but it seemed useful to be explicit about my concerns. On Sun, 7 May 2017 00:55:51 +0800 C Bergstrom <cbergstrom at pathscale.com> wrote: > You don't seem to be listening, but one last try. I listened. I respectfully disagree. > If you have a FE related question - Ask on cfe-dev and if you don't > get a response I'd be surprised. I

> On Feb 21, 2017, at 9:54 PM, Nemanja Ivanovic via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I believe that providing additional intrinsics that would directly produce the ISD::ADDC/ISD::SUBC nodes would provide the additional advantage of being able to directly produce these nodes for code that doesn't have anything to do with multiprecision addition/subtraction. I am

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

On Monday 23 November 2009 09:01, Anton Korobeynikov wrote: > Hello > > > It is a RISC with around 60 instructions like a 80c51 instruction set > > (without mul/div) and with Direct or indirect memory acces. > > My estimate is something like a man-week for a person, who knows what to do > :) That's pretty optimistic, even for someone who knows what to do. The

Please add to the ProjectsWithLLVM/ page. Thanks. ==== Embedded System Language (ESL) ESL <code.google.com/p/esl/> is a new programming language designed to be used for efficient programming of embedded systems and other low-level system programming projects. ESL is a typed compiled language with features that allow the programmer to dictate the concrete representation of data values;

Would someone be so kind as to tell me what the status of debugging symbols (DWARF) generated by clang/llvm is? I am on a linux x86-64 system (Fedora 13). Is gdb supposed to understand the generated DWARF? When I generate an executable with "clang -g" followed by "llc -O0" and feed it to gdb, I get "no debugging symbols found". What is the status of lldb on

On 23 November 2010 18:03, Bagel <bagel99 at gmail.com> wrote: > Would someone be so kind as to tell me what the status of debugging symbols > (DWARF) generated by clang/llvm is? Hi Bagel, It should be fairly complete... > When I generate an executable with "clang -g" followed by "llc -O0" and feed it > to gdb, I get "no debugging symbols found".

I won't work at full time on this project and I fear the first week is used to read documentations :) The better way to have an idea is to start backend developement. I'll try to work on this backend for a month and will see if I'm on the right way. 2009/11/24 Evan Cheng <evan.cheng at apple.com> > > On Nov 24, 2009, at 8:30 AM, David Greene wrote: > > > On

Hello, this morning I apparently had tinc crash on me. In 2 independent tinc clusters of 3 nodes each (but located in the same datacenter), one tinc process crashed in each of the clusters. One process apparently with `status=6/ABRT`, the other with `status=11/SEGV`. Interestingly, they crashed with only 5 minutes difference. The only thing I can come up with that might explain this correlation

I'm having some trouble with placing some iax calls over an openvpn: Setup A is a 1.8GHz Celeron, T100P attached to a Zhone Zplex. Setup B is a 266MHz P2, T100P attached to a Zhone Zplex. Setup C is a 700MHz P3, T100P attached to an Adtran TA 750. Setup D is a 233MHz Pentium, with an X100P. Setups A and B are on the same physical network. IAX calls routed between them work fine. Setup D is