<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 22, 2014 at 9:50 AM, Jack Howarth <span dir="ltr"><<a href="mailto:howarth.mailing.lists@gmail.com" target="_blank">howarth.mailing.lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Nico,<div> A simple review of cfe-commits mailing list archive for the past couple of months shows that Alexey Bataev has been regularly committing sections of the clang-omp merge so it really isn't true to say that nothing has landed in trunk yet.</div>
</div></blockquote><div><br></div><div>Oh sure, anything that was committed by yesterday is part of 3.5. I think Bill understood your question as "We landed this bit of code very recently that we'd like to merge", but from what I understand it's more "there's a largeish chunk of code in some upstream repo". I don't think Bill meant to say that all that unmerged code should just be merged to 3.5 :-)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div> It is unfortunate that the clang-omp changes were never submitted as a complete series of patches on the mailing list so only the clang-omp developers have a good sense of what remains to be committed from their tree.</div>
<span class="HOEnZb"><font color="#888888">
<div> Jack</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 22, 2014 at 12:41 PM, Nico Weber <span dir="ltr"><<a href="mailto:thakis@chromium.org" target="_blank">thakis@chromium.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Tue, Jul 22, 2014 at 9:38 AM, Bill Wendling <span dir="ltr"><<a href="mailto:isanbard@gmail.com" target="_blank">isanbard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jack,<br>
<br>
Please go ahead and merge those changes into the 3.5 release.</blockquote><div><br></div></div><div>They aren't landed yet on trunk, as far as I understand.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There’s still time before we close the branches to non-bug fix changes.<br>
<br>
-bw<br>
<div><br>
On Jul 22, 2014, at 9:25 AM, Jack Howarth <<a href="mailto:howarth.mailing.lists@gmail.com" target="_blank">howarth.mailing.lists@gmail.com</a>> wrote:<br>
<br>
> Is the merge of the clang-omp changes being abandoned for the 3.5 release or will these additional changes to trunk also be allowed into the clang 3.5 branch? If official clang 3.5 release is left with only a partial merge of these changes, it would seem to require upstream to pause and rebase their clang-omp tree on clang 3.5 instead of the current clang 3.4 (to allow for a stable release of clang-omp to be available based on clang 3.5).<br>
</div></blockquote><div><br></div></div><div>This is probably correct, yes.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
> Jack<br>
</div>> _______________________________________________<br>
> cfe-dev mailing list<br>
> <a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
> <a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
<br>
<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@cs.uiuc.edu" target="_blank">cfe-dev@cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br>
</blockquote></div></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>