similar to: [LLVMdev] Potential Google Summer of Code Applicant

On 04/02/2012 05:41 AM, Patrick Edwards wrote: > Hi, my name is Patrick Edwards, and I'm currently a CS major at Kent > State University. I have always been interested in doing work with > compilers and LLVM seems to be a perfect fit for me to learn more over > the summer, and also contribute to open-source projects at the same > time. However, while browsing through the project

+cfe-dev, +chandlerc On Mon, Apr 2, 2012 at 11:05 AM, Tobias Grosser <tobias at grosser.es> wrote: > On 04/02/2012 05:41 AM, Patrick Edwards wrote: >> >> Hi, my name is Patrick Edwards, and I'm currently a CS major at Kent >> State University. I have always been interested in doing work with >> compilers and LLVM seems to be a perfect fit for me to learn more

I would really like to see someone work on LLVM's garbage collection support - it hasn't been updated in 4 years, and while there's been a lot of talk about ways that it could be improved, there's been no action. On Sun, Apr 1, 2012 at 8:41 PM, Patrick Edwards <pedwar11 at kent.edu> wrote: > Hi, my name is Patrick Edwards, and I'm currently a CS major at Kent State

On 4/6/12 2:21 AM, Talin wrote: > I would really like to see someone work on LLVM's garbage collection > support - it hasn't been updated in 4 years, and while there's been a > lot of talk about ways that it could be improved, there's been no action. That is *sooo* true! :-) I'm one of the authors of an LLVM backend for Erlang (ErLLVM [1]); we have tested and

On 04/02/2012 11:21 AM, Manuel Klimek wrote: > +cfe-dev, +chandlerc > > On Mon, Apr 2, 2012 at 11:05 AM, Tobias Grosser<tobias at grosser.es> wrote: >> On 04/02/2012 05:41 AM, Patrick Edwards wrote: >>> >>> Hi, my name is Patrick Edwards, and I'm currently a CS major at Kent >>> State University. I have always been interested in doing work with

Hi, I'm currently working for the next 6 months, but I would be very interested in looking into this. Are there any discussions in this mailing list that would be useful in finding out more information? Regards Michael Thorpe Internet Services Developer Netcraft Ltd -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Yiannis

Sorting through all of the discussions would be difficult, as the ideas have morphed over the years. Also, some of the discussion took place offline at various LLVM dev conferences. I can summarize the main points here: The biggest improvement in GC would be to allow SSA values to be declared as GC roots - currently only alloca values, that is, values in memory, can be GC roots. This means that

I realize that this was written in a hurry, and may not have been entirely clear. If there are any questions, critiques, etc., I'd be happy to respond to them. I'd really like it if LLVM's garbage collection support didn't continue to languish... On Fri, Apr 6, 2012 at 12:43 PM, Talin <viridia at gmail.com> wrote: > Sorting through all of the discussions would be

Just a thought, but it would it make sense for garbage collection to be some sort of minimal debug information for potentially optimized code. Store just enough debug information to reconstruct call stacks and know where gc-roots are. Perhaps an approach like this could minimize the work required as it is shared between gc-support and debug information support. >From what I understand, DWARF

Actually, I'm pretty happy with the way that LLVM handles this aspect of garbage collection now. LLVM does not itself generate any data related to garbage collection - all it does is supply a plugin interface that lets your code know where on the stack the roots are. Your code is responsible for generating any static data structures that would be read by your garbage collector. So if you

Sorry for double-posting to the list, The citation is the following (this time with a url to the paper): K. Sagonas, C. Stavrakakis, and Y. Tsiouris. "ErLLVM: An LLVM backend for Erlang"[1]. In Eleventh ACM SIGPLAN Erlang Workshop, September 2012. ACM Press. Thanks! Yiannis [1]: http://erllvm.softlab.ntua.gr/files/erlang03-sagonas.pdf On 09/07/2012 08:13 PM, Yiannis Tsiouris wrote:

ping. :-) On 09/07/2012 08:24 PM, Yiannis Tsiouris wrote: > [...] > The citation is the following (this time with a url to the paper): K. > Sagonas, C. Stavrakakis, and Y. Tsiouris. "ErLLVM: An LLVM backend > for Erlang"[1]. In Eleventh ACM SIGPLAN Erlang Workshop, September > 2012. ACM Press. > > [1]: http://erllvm.softlab.ntua.gr/files/erlang03-sagonas.pdf >

Hi, We 've been working on an LLVM backend for High Performance Erlang (HiPE) [1], the native code compiler of Erlang/OTP [2]. ErLLVM [3] targets the X86 and AMD64 architectures for now but there is some ongoing work from a team on the Uppsala University to also support ARM. In our implementation, we have paid special attention on retaining ABI-compatibility with the Erlang Runtime System in

> Ah OK. I would have loved to have such a tool, but as a non-clang > expert, I can obviously not judge if it is suited. Maybe you are aware > of other projects suitable for GSoC, But still many things in "Use clang libraries to implement better versions of existing tools" are doable as it seems to me. E.g. delta replacement based on clang. -- With best regards, Anton

Hi, Following Chris' advice, I will rebase the patches and break them in 3 distinct emails (one at a time) in order to be easier for a reviewer to approve/comments. Please note that the three patches while being code-wise independent, they 're strongly-connected *semantically*, meaning that including just a subset of these patches to LLVM's code base is quite weak if the others are

On Apr 2, 2012, at 3:07 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> Ah OK. I would have loved to have such a tool, but as a non-clang >> expert, I can obviously not judge if it is suited. Maybe you are aware >> of other projects suitable for GSoC, > But still many things in "Use clang libraries to implement better > versions of existing

On Tue, Apr 3, 2012 at 11:37 AM, Jim Grosbach <grosbach at apple.com> wrote: > > On Apr 2, 2012, at 3:07 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > >>> Ah OK. I would have loved to have such a tool, but as a non-clang >>> expert, I can obviously not judge if it is suited. Maybe you are aware >>> of other projects suitable for GSoC,

This patch (and the others that will follow) are rebased on svn r155440: "AVX2: The BLENDPW instruction selects between vectors of v16i16 using an i8 immediate. We can't use it here because the shuffle code does not check that the lower part of the word is identical to the upper part" Patch 1/3: The attached commits add a new calling convention to support the LLVM backend for

Hello, hopefully this is the correct place to ask this... We use distcc with clang++ and I have recently added -Wunreachable-code to our set of warnings.  The problem I am seeing is the compile fails with (valid) unreachable code warnings on the slave, but passes (no warning) locally.  All machines have the same compiler version clang version 8.0.1-svn369350-1~exp1~20190820121219.79

Per http://rwiki.sciviews.org/doku.php?id=developers:projects:gsoc2010 -- and http://rwiki.sciviews.org/doku.php?id=developers:projects:gsoc2010:syrfr -- I am applying to mentor the "Symbolic Regression for R" (syrfr) package for the Google Summer of Code 2010. I propose the following test which an applicant would have to pass in order to qualify for the topic: 1. Describe each of the