<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:57 AM Zachary Turner <<a href="mailto:zturner@google.com">zturner@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Doesn't that defeat the entire point of the mono-repo though?</div></blockquote><div><br>No - this advise already exists even when committing two independent changes in a single repo in LLVM. Independent changes should generally be committed independently - makes it easier to understand them through the commit history, to revert/reapply if needed, etc.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="m_2168798587748775815inbox-inbox-Apple-converted-space"> </span> Committing them separately in the current mono-repo is a lot of extra work, which people have already spent a lot of time writing tooling for to make it as easy as possible to commit everything "all at once" (which leads to this scenario). Going back on that seems contrary to the direction of the mono-repo.<div><br></div><div>I think it would be all the more reason to finalize the transition to the mono-repo more quickly so that they're not actually separate repos on the backend and then they show up as one commit.</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:52 AM David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:51 AM Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ahh, I'm using the mono-repo. When I do one cross-repo commit it creates one commit in each repo with an identical message. Not sure if there's a better solution,</div></blockquote></div></div><div dir="ltr"><div class="gmail_quote"><div><br>All the more reason to commit independent changes independently, I would think<br> </div></div></div><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"> seems like more and more people are switching to mono-repo for daily workflow.</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:48 AM David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ah, this was a build break fix?<br><br>Perhaps I've been confused by the cross-repo commit. Two changes with the same change description, fixing two independent things in two different repos... I thought they were related (that the fix in LLVM was fixing/changing the test output in the lld test), but I guess they weren't?<br><br>Might be better to commit such things separately, with separate/specific descriptions.</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:38 AM Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">A test for what, specifically?</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 10, 2017 at 10:20 AM David Blaikie <<a href="mailto:dblaikie@gmail.com" target="_blank">dblaikie@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Looks like there should be a test for this in the LLVM tree, if that's where the functionality is (with a committed PDB file or similar (if there's a convenient YAML format or something, that's OK too), as llvm-dwarfdump is tested)</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jul 7, 2017 at 12:00 PM Zachary Turner via llvm-commits <<a href="mailto:llvm-commits@lists.llvm.org" target="_blank">llvm-commits@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Author: zturner<br>
Date: Fri Jul 7 12:00:06 2017<br>
New Revision: 307426<br>
<br>
URL: <a href="http://llvm.org/viewvc/llvm-project?rev=307426&view=rev" rel="noreferrer" target="_blank">http://llvm.org/viewvc/llvm-project?rev=307426&view=rev</a><br>
Log:<br>
[llvm-pdbutil] Fix build.<br>
<br>
Some platforms require an explicit specialization of std::hash<br>
for PdbRaw_FeaturesSig. Also a test involving case sensitivity<br>
needed to be fixed. For now that particular check just accepts<br>
any path even if they're completely different. Long term we<br>
should output paths in the correct case to match MSVC.<br>
<br>
Modified:<br>
llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h<br>
<br>
Modified: llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h<br>
URL: <a href="http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h?rev=307426&r1=307425&r2=307426&view=diff" rel="noreferrer" target="_blank">http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h?rev=307426&r1=307425&r2=307426&view=diff</a><br>
==============================================================================<br>
--- llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h (original)<br>
+++ llvm/trunk/tools/llvm-pdbutil/DiffPrinter.h Fri Jul 7 12:00:06 2017<br>
@@ -13,12 +13,23 @@<br>
#include "llvm/ADT/ArrayRef.h"<br>
#include "llvm/ADT/StringMap.h"<br>
#include "llvm/ADT/StringRef.h"<br>
+#include "llvm/DebugInfo/PDB/Native/RawConstants.h"<br>
#include "llvm/Support/FormatVariadic.h"<br>
#include "llvm/Support/raw_ostream.h"<br>
<br>
#include <list><br>
#include <unordered_set><br>
<br>
+namespace std {<br>
+template <> struct hash<llvm::pdb::PdbRaw_FeatureSig> {<br>
+ typedef llvm::pdb::PdbRaw_FeatureSig argument_type;<br>
+ typedef std::size_t result_type;<br>
+ result_type operator()(argument_type Item) const {<br>
+ return std::hash<uint32_t>{}(uint32_t(Item));<br>
+ }<br>
+};<br>
+} // namespace std<br>
+<br>
namespace llvm {<br>
namespace pdb {<br>
<br>
<br>
<br>
_______________________________________________<br>
llvm-commits mailing list<br>
<a href="mailto:llvm-commits@lists.llvm.org" target="_blank">llvm-commits@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-commits</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div></div></blockquote></div>
</blockquote></div></div>