Hello,
I am working on zero-tuple support. Although, I don't have any useful input
to provide at this point in time.
I am tied up at the moment because of my exams. I will update you regularly
regarding my progress.
Thank you,
Rajath Shashidhara
On Fri, Mar 11, 2016 at 8:48 PM, Michael Ferguson <mfergu...@cray.com>
wrote:
> Hi -
>
> Other resources for starting to work inside the compiler are
> in CompilerIRTricks.txt and CompilerDebugging.txt :
>
> https://github.com/chapel-lang/chapel/blob/master/doc/developer/bestPractic
> es/CompilerIRTricks.txt and
>
> https://github.com/chapel-
> lang/chapel/blob/master/doc/developer/bestPractices/CompilerDebugging.txt
>
>
> -michael
>
> On 3/11/16, 8:21 AM, "Michael Ferguson" <mfergu...@cray.com> wrote:
>
> >Hi Rohan -
> >
> >On 3/11/16, 4:32 AM, "Rohan Badlani" <rohan.badl...@gmail.com> wrote:
> >
> >>It would be great if you could direct me a few good resources explaining
> >>the Compiler Design for Chapel and also let me know if there are any
> >>bugs/tasks that I could try out to get hands on experience with the
> >>compiler code.
> >
> >
> >See
> >
> https://github.com/chapel-lang/chapel/tree/master/doc/developer/compilerOv
> >e
> >rview
> >for an overview of the compiler. This document is a little bit old, so
> >some details
> >might be wrong, but I believe it is still an accurate summary of the
> >compiler's
> >overall architecture.
> >
> >For tasks to get experience, see
> >
> > http://chapel.cray.com/gsoc/contributing.html
> >
> >For more information on getting experience working on the compiler
> >specifically... as the contributing page says, we caution you that
> >the compiler is not the easiest place to start. Nonetheless I will
> >share some thoughts about tasks you could try.
> >
> >Bugs in the compiler are listed sometimes as JIRA issues and sometimes
> >as .future files in the test system. For a start, I might recommend
> >finding a 'error message' .future in the test system and trying to
> >adjust the error message. You could also search for 'bug' or
> >'feature request' futures, but these might be more involved.
> >
> >E.g. you could use
> > find test -name '*.future' | xargs grep "error message"
> >
> >
> >to find these. Note that some of these error messages are coming from
> >Chapel module code rather than the compiler itself.
> >
> >Other than that - perhaps trying to get the compiler to accept
> >zero-length tuples. I don't know how hard it will be.
> >
> >Rajath, I brought up zero-length tuples in another discussion
> >with you. Are you already working on it?
> >
> >Cheers,
> >
> >-michael
> >
> >
> >--------------------------------------------------------------------------
> >----
> >Transform Data into Opportunity.
> >Accelerate data analysis in your applications with
> >Intel Data Analytics Acceleration Library.
> >Click to learn more.
> >http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> >_______________________________________________
> >Chapel-developers mailing list
> >Chapel-developers@lists.sourceforge.net
> >https://lists.sourceforge.net/lists/listinfo/chapel-developers
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Chapel-developers mailing list
> Chapel-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/chapel-developers
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Chapel-developers mailing list
Chapel-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/chapel-developers
