<div dir="ltr">If the "pre-merge checks" presentation from recent dev-meeting [1] is to be believed, many revisions proposed for review fail build/tests. But now that we have those checks, hopefully John's experience for plucking an arbitrary commit from main might give better results than in years past.<div><br></div><div>Another approach might be to review the buildbots to find a commit that is green across the board.<br><div><br></div><div>[1] <a href="https://llvm.org/devmtg/2020-09/slides/Goncharov-Pre-merge_checks.pdf">https://llvm.org/devmtg/2020-09/slides/Goncharov-Pre-merge_checks.pdf</a><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 12, 2021 at 9:02 PM Neil Nelson via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<font size="-1">Not aware that main is broken in many of the test
suites. It will be helpful to provide the bugs you find. Or if you
can provide a command sequence I can do that here on Ubuntu.</font>
<p><font size="-1">Perhaps if you give specific detail about the
issues you are facing it will allow the other contributors to
make suggestions.</font><br>
</p>
<p><font size="-1">Neil Nelson<br>
</font></p>
<div><font size="-1">On 3/12/21 4:50 PM,
John Byrd via llvm-dev wrote:</font><br>
</div>
<blockquote type="cite">
<div dir="ltr">Dear llvm,
<div><br>
</div>
<div>A few of us are working on a novel LLVM backend in a
separate repository, and our new branch uses a lot of the
fancy new MLIR stuff. We'd like the group's opinions as to
best practices for keeping in sync with llvm's main branch.</div>
<div><br>
</div>
<div>Some of us opine that we should be periodically rebasing
our backend on the tip of main. This has the advantage that
we benefit from new main features, but it has the disadvantage
that main seems to usually be broken in many of the test
suites. So it's hard to find a stable commit in main, which
passes all the tests on all the buildbots, that we can rebase
onto.</div>
<div><br>
</div>
<div>And some of us opine that we should be merging our work
with main. This has the advantage that we never rewrite
history, but it also means that it will be painful to squash
or rebase our commits, if we ever decide to submit our work
upstream.</div>
<div><br>
</div>
<div>We've considered doing our work based on one of the release
branches, but until recently the development docs recommended
against this.</div>
<div><br>
</div>
<div>Wisdom would be appreciated; thank you.<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">---<br>
<br>
John Byrd<br>
Gigantic Software<br>
2321 E 4th Street<br>
Suite C #429<br>
Santa Ana, CA 92705-3862<br>
<a href="http://www.giganticsoftware.com" target="_blank">http://www.giganticsoftware.com</a><br>
T: (949) 892-3526 F: (206) 309-0850</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
LLVM Developers mailing list
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">-Brian</div>