similar to: [LLVMdev] Google Summer of Code Idea

Dear LLVM-Dev, Your ideas page said that you'd take applications to write new language frontends for LLVM. I've been in-progress for most of a year now writing a compiler for my language Deca as a side-project, and I'd like to make it GSOC project by targeting it at LLVM. My other commitments are that I've applied to several different REU programs. If one of them

2010/3/20 Louis Gerbarg <lgerbarg at gmail.com> > On Fri, Mar 19, 2010 at 3:47 PM, Chris Lattner <clattner at apple.com> wrote: > >> >> On Mar 19, 2010, at 11:08 AM, 琬菁楊 wrote: >> >> >> Hello Tristan and all, >> >> I have already know that if I want to do this feature(c -> EFI Byte code) >> for GCC >> I should further

On Fri, Mar 19, 2010 at 3:47 PM, Chris Lattner <clattner at apple.com> wrote: > > On Mar 19, 2010, at 11:08 AM, 琬菁楊 wrote: > > > Hello Tristan and all, > > I have already know that if I want to do this feature(c -> EFI Byte code) > for GCC > I should further modify the GCC front end(parser) to solve the problem (the > size > of pointer is determined at

This email is written on the premise that LLVM will be involved in GSOC again this year. I noted that the wiki's open projects page [0] has several possible projects, that seem suitable for a summer of code project. I am writing this email to this list with the hope of getting some feedback on specifics for a GSOC application, and also wondering if any potential mentors are interested in

On Mar 19, 2010, at 11:08 AM, 琬菁楊 wrote: > > Hello Tristan and all, > > I have already know that if I want to do this feature(c -> EFI Byte code) for GCC > I should further modify the GCC front end(parser) to solve the problem (the size > of pointer is determined at run time). > > I have read a powerpoint about LLVM

Dear all, I would like to propose an average technical project that might have a great use in many parts/derivatives of LLVM, including ours. Consider you have dozens of regression tests in high-level languages, reporting whether or not the recent changes in compiler are breaking some kind of loop handling (vectorization, parallelization, etc.). Consider you have a post-processing utility, which

On Thu, Feb 28, 2008 at 1:43 PM, Richard Warburton <richard.warburton at gmail.com> wrote: > This email is written on the premise that LLVM will be involved in > GSOC again this year. I noted that the wiki's open projects page [0] > has several possible projects, that seem suitable for a summer of code > project. I am writing this email to this list with the hope of >

Hello Tristan and all, I have already know that if I want to do this feature(c -> EFI Byte code) for GCC I should further modify the GCC front end(parser) to solve the problem (the size of pointer is determined at run time). I have read a powerpoint about LLVM ( http://llvm.org/pubs/2008-10-04-ACAT-LLVM-Intro.pdf) It is the LLVM-GCC design graph (

On Feb 28, 2008, at 10:43 AM, Richard Warburton wrote: > This email is written on the premise that LLVM will be involved in > GSOC again this year. I hope so too! > I would be looking to implement a context-sensitive alias analysis. > Whilst I accept that this isn't the most efficient category of alias > analysis, I think the implementation of such an analysis, that trades

Ramón García wrote: > I would like to see the code of your front end. > > It should be available in a week or two. I'm currently dealing with licensing issues. > I started working with llvm-java, since it was what was available. It > does not run yet (small compilation issues, almost done), > but the design seems fine. It can run (when setup complete) small > pieces

Hello all, I am highly interestd in implementing C compiler for EFI Byte Code in LLVM and participate in Google Summer Code. EFI is a much larger, more complex,OS-like replacement for the older BIOS firmware interface present in all IBM PC-compatible personal computers. and the EFI specification provides for a processor-independent device driver environment(like virtualmachine), called EFI Byte

As I told you, I am working with the Java frontend. Currently I am working with the code from http://llvm.org/svn/llvm-project/java/. The first task has been to put it up to date, since it was written for LLVM 1.9 and there are few incompatibilities. This is mostly done. How can I submit a patch? I am interested to get this work funded by a Google summer of code grant. Is there anyone interested

Nicolas Geoffray wrote: > > There is no real missing feature. The VMs can execute standard > applications (last time I checked, the JVM can run tomcat), and the > implementations follow the VM specifications. The CLI implementation > lacks generics and overflow detection, but this is not top priority in > my mind. > > Among many features, here are the ones that I'd

Hi Scott, On 18 Mar 2007, at 04:22, Scott Fortmann-Roe wrote: > Hi, > > I noticed that LLVM had signed up as a mentoring organization for > Google's summer of code. LLVM looks like an exciting project that > overlaps some of my interests. > > I would be interested in developing an additional front end for a > language it does not currently support (I'm open to

Good day, earlier this month I wrote you this email: Good evening, my name is Miroslav Hnčíř and I am from Czech Republic. I would like to participate in Google Summer of Code and help the LLVM project. I also would like to continue work on LLVM after GSoC, regardless of the outcome. I am really interested in compilers and especially in LLVM (backends interest me more), but my problem is that I do

Hello, Chris > 2010/3/20 Chris Lattner <clattner at apple.com> > > >> On Mar 19, 2010, at 2:40 PM, Louis Gerbarg wrote: >> >> >>> What do you mean by "variable sized pointers"? What does: >>> >>> struct S {void *X; }; >>> >>> return for sizeof(struct S); ? >>> >> >> It doesn't, at

Hello, Ramon > As I told you, I am working with the Java frontend. Currently I am > working with the code from http://llvm.org/svn/llvm-project/java/. The > first task has been to put it up to date, since it was written for > LLVM 1.9 and there are few incompatibilities. This is mostly done. How > can I submit a patch? Just post the patch into llvm-commits mailing list. > I am

On 10 March 2010 16:57, 琬菁楊 <ching1119.cs96 at g2.nctu.edu.tw> wrote: > I think the main issue is that EFI C dialect is not ANSI-C compliant: the > size of pointer is determined at the run-time and therefore the layout of > the structure is not static. Does LLVM support this model? Hi Ching, The LLVM IR doesn't care about the size of your pointers, and this is why you have the

On Mon, Mar 15, 2010 at 10:50 AM, Renato Golin <rengolin at systemcall.org> wrote: > On 10 March 2010 16:57, 琬菁楊 <ching1119.cs96 at g2.nctu.edu.tw> wrote: >> I think the main issue is that EFI C dialect is not ANSI-C compliant: the >> size of pointer is determined at the run-time and therefore the layout of >> the structure is not static. Does LLVM support this

Hi, I'm Hiroyuki Katsura. I will contribute to libguestfs as a Google Summer of Code project. I'll start to develop from next week. I'm going to work on the project "Create Rust bindings for libguestfs." Project summary is available here. https://summerofcode.withgoogle.com/projects/#6730007286644736 Now, I'll show you the detail of the project. This is the reprint of