<div dir="ltr">Alp,<div> Its obvious we have started off on the wrong foot here. Please lets not fixate on any objections that you had to my initial posts and try to have a productive interaction here. As far as I know, everyone here has the same goal of seeing clang-omp/openmp land in an llvm release as soon as feasible. I am just relating what I have observed of the social dynamics of the review process from over on FSF gcc. While it is a different system, it still is the same sort of pool of varied personalities with the same random conflicts (as by testified by how poorly we have hit it off).</div>
<div> Jack</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 2, 2014 at 12:41 PM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 02/06/2014 18:17, Andrey Bokhanko wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
Alp,<br>
<br>
With all respect, a few of assertions you made are simply *not true*.<br>
<br></div><div class="">
On Mon, Jun 2, 2014 at 6:02 PM, Alp Toker <<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a> <mailto:<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>>> wrote:<br>
<br>
It should be made clear that the current OpenMP runtime CMake<br>
build system has been in development for some time, including<br>
on-list discussions in the LLVM community that go back weeks<br>
following all the best practices we have. The only thing that<br>
changed is that C. Bergstrom graciously provided the sign-off we<br>
needed to integrate Jack's work late last week.<br>
<br>
<br>
What "discussions... that go back weeks" you are speaking about?!<br>
</div></blockquote>
<br>
<br>
In this case we have had a review period spanning three days, with feedback from three developers including an *OpenMP expert* (and final review from technically the *top committer* on the LLVM openmp module given that the "code drop" commit was monolithic), following *three iterations* of the patch posted to the list for public scrutiny and amendments. This is unequivocally a *good thing*.<br>
<br>
If you doubt that, take a look at the previous non-trivial commits and "code dumps" -- now tell me, which sounds like best practice between the two?<div class=""><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Jack started his "On Improving the Build System revisited" thread on May 30. This is four days ago, not weeks.<br>
</blockquote>
<br></div>
The plan to introduce the CMake build system originated months ago and the original code was written before then, but not signed off until last week.<br>
<br>
This has been coordinated in full openness.<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
And since when "all the best practices" include introducing a new build system without getting project architect's consent? -- especially after explicitly asked to do so, a message that you conveniently ignored.<br>
<br>
So it's a mischaracterisation to say this happened over the<br>
weekend. Even if it did that would be on the long side compared to<br>
timescales seen on llvm-commits.<br>
<br>
<br>
What timescales you are speaking about?!<br>
</blockquote>
<br></div>
Reviews on cfe-commits frequently happen faster than the *15 minute* mailing list delay which causes commits to arrive before the patch proposal. Not always great but we deal with it. You are actually free to suggest and provide improvements after a change has landed.<div class="">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For reference, we wait for *weeks* for our OpenMP in clang patches to be reviewed! And we commit them *only* after explicit consent of one of clang code owners -- even if we already got code review from someone else.<br>
</blockquote>
<br></div>
And we're trying to improve that workflow. Who wants to wait for *weeks* when we have qualified reviewers?<div class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In general it's a good idea to participate in on-list discussions<br>
and give a heads up if you see people discussing features you have<br>
plans for. Is there anything else in the pipeline?<br>
<br>
<br>
That's *exactly* what we did back in March.<br>
<br>
<a href="http://lists.cs.uiuc.edu/pipermail/openmp-dev/2014-March/000055.html" target="_blank">http://lists.cs.uiuc.edu/<u></u>pipermail/openmp-dev/2014-<u></u>March/000055.html</a><br>
</blockquote>
<br></div>
You asked about "Cmake generating gmake makefiles?" in that mail and the community has responded.<br>
<br>
Also note that the one commit below is all we actually know about your work and your relation is to the project -- your mail was arrogant enough that I wouldn't have responded were it not for your association with Jim Cownie who we know and work with, and the unfortunate attitude towards people who have helped the project. Note that I've offered to give my own time to help Jim merge your CMake changes with the system in ToT because it's a nice thing to do.<br>
<br>
<br>
$ git log --author=Andrey<br>
commit c88ab54e0d3d89c97175d21d6af346<u></u>6df5445eaa<br>
Author: Andrey Churbanov <<a href="mailto:Andrey.Churbanov@intel.com" target="_blank">Andrey.Churbanov@intel.com</a>><br>
Date: Thu Oct 3 07:27:25 2013 +0000<br>
<br>
typo fixed as a test commit<br>
<br>
<br>
Alp.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Yours,<br>
Andrey<br>
<br>
</blockquote><div class="im HOEnZb">
<br>
-- <br>
<a href="http://www.nuanti.com" target="_blank">http://www.nuanti.com</a><br>
the browser experts<br>
<br></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Openmp-dev mailing list<br>
<a href="mailto:Openmp-dev@dcs-maillist2.engr.illinois.edu" target="_blank">Openmp-dev@dcs-maillist2.engr.<u></u>illinois.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/openmp-dev</a><br>
</div></div></blockquote></div><br></div>