<div dir="ltr"><div>Hi again.<br><br></div><div>I've though more about the full standard being too ambitious, and now I fully agree with that. So I had a go at choosing the useful subset of Fortran on which I would like to work on - my update proposal can be viewed at <a href="https://gist.github.com/hyp/5434845">https://gist.github.com/hyp/5434845</a> .<br>
</div><div>Focusing on less should also improve my productivity and lead to a better summer of code project by drastically reducing the pressure :)<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/4/22 Alex L <span dir="ltr"><<a href="mailto:arphaman@gmail.com" target="_blank">arphaman@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>Thanks for the responses!<br></div><div class="im"><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">I might be wrong (I'd love to be wrong here!) but I think this is a bit too ambitious<br>
</blockquote></div> You might be right about it being too ambitious, it would certainly be wise to aim for less. A more polished, but less broad product is definitely better than a buggy standard compliant one, and I think that it would go better with the general philosophy of GSoC. I will take this fact into consideration for the revised proposal.<div class="im">
<br>
<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Also, in your proposal, it looks as though you're not writing tests
until the end; tests need to be written as soon as the features are
testable.<br></blockquote></div><div> That's kind of true, but I actually planned on writing tests during feature development, it's just that these tests wouldn't cover everything and should be expanded and tested fully towards the end of GSoC. I should definitely mention that in my plan.<br>
<br></div><div> As for the tooling support, I guess that it wouldn't hurt to take the fact that tools should be integrated with flang in the future into account during the development. I will take a look on how clang and various tools for it operate.<br>
</div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/4/22 Hal Finkel <span dir="ltr"><<a href="mailto:hfinkel@anl.gov" target="_blank">hfinkel@anl.gov</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>----- Original Message -----<br>
> From: "Dmitri Gribenko" <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>><br>
> To: "Alex L" <<a href="mailto:arphaman@gmail.com" target="_blank">arphaman@gmail.com</a>><br>
> Cc: "LLVM Developers Mailing List" <<a href="mailto:llvmdev@cs.uiuc.edu" target="_blank">llvmdev@cs.uiuc.edu</a>><br>
> Sent: Monday, April 22, 2013 9:00:51 AM<br>
> Subject: Re: [LLVMdev] GSoC project questions.<br>
><br>
</div><div>> On Mon, Apr 22, 2013 at 4:30 PM, Alex L <<a href="mailto:arphaman@gmail.com" target="_blank">arphaman@gmail.com</a>> wrote:<br>
> > Thanks for your support.<br>
> > I wrote my draft GSoC proposal, it can be viewed here -<br>
> > <a href="https://gist.github.com/hyp/5434845" target="_blank">https://gist.github.com/hyp/5434845</a><br>
> > Please read it and tell me what you think. Any criticisms or<br>
> > suggestions are<br>
> > welcome!<br>
><br>
> Hello Alex,<br>
><br>
> > I plan to make flang a fully featured frontend which fully supports<br>
> > Fortran 77<br>
><br>
> I might be wrong (I'd love to be wrong here!) but I think this is a<br>
> bit too ambitious. Given that you have to write tests *as you<br>
> implement the features*, handle corner cases (and one has to actually<br>
> discover corner cases from the standard, if one is not familiar with<br>
> Fortran) and produce diagnostics for invalid code, I don't think it<br>
> is<br>
> possible to implement all of the frontend + codegen within 12 weeks.<br>
<br>
</div>Alex, I agree with Dmitri, I think that the proposal sounds a little too ambitious. Maybe everything will go smoothly and you'll be able to accomplish everything that you'd like, but we should plan for less. I favor identifying a useful subset (such as that needed for BLAS) and focusing on doing a really good job on that subset rather than trying to get full feature coverage. In my experience, coding tests and high-quality warning/error messages takes more time than coding the feature itself. Also, in your proposal, it looks as though you're not writing tests until the end; tests need to be written as soon as the features are testable.<br>
<br>
Regarding motivation, I would also like to bring the same kind of "tooling" (analysis and transformation) support available in Clang to Fortran. Not that this specifically impacts your project, but I think is an important part of the longer-term motivation for developing an LLVM Fortran frontend.<br>
<br>
I am glad that you're excited about working on this project!<br>
<span><font color="#888888"><br>
-Hal<br>
</font></span><div><br>
><br>
> Dmitri<br>
><br>
> --<br>
> main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
> (j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
</div><div><div>> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>