<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 13, 2016, at 5:56 PM, Saleem Abdulrasool <<a href="mailto:compnerd@compnerd.org" class="">compnerd@compnerd.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">On Mon, Jun 13, 2016 at 5:01 PM, Mehdi Amini via lldb-dev<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:lldb-dev@lists.llvm.org" target="_blank" class="">lldb-dev@lists.llvm.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><span class=""><br class="">> On Jun 13, 2016, at 4:54 PM, Hans Wennborg <<a href="mailto:hans@chromium.org" class="">hans@chromium.org</a>> wrote:<br class="">><br class="">> Breaking this out into a separate thread since it's kind of a separate<br class="">> issue, and to make sure people see it.<br class=""><br class=""></span>Thanks!<br class=""><span class=""><br class="">><br class="">> If you have opinions on this, please chime in. I'd like to collect as<br class="">> many arguments here as possible to make a good decision. The main<br class="">> contestants are 4.0 and 3.10, and I've seen folks being equally<br class="">> surprised by both.<br class="">><br class="">> Brain-dump so far:<br class="">><br class="">> - After LLVM 1.9 came 2.0, and after 2.9 came 3.0; naturally, 4.0<br class="">> comes after 3.9.<br class="">><br class="">> - There are special bitcode stability rules [1] concerning major<br class="">> version bumps. 2.0 and 3.0 had major IR changes, but since there<br class="">> aren't any this time, we should go to 3.10.<br class="">><br class="">> - The bitcode stability rules allow for breakage with major versions,<br class="">> but it doesn't require it, so 4.0 is fine.<br class=""><br class=""></span>(basically repeating my point of the other thread here)<br class="">Bumping the major version number without changing the bitcode compatibility rule would mean dropping the current guarantee on this aspect. I doubt we want to go this route without a good reason.<br class=""></blockquote><div class=""><br class=""></div><div class="">Completely agree with you here: unless we have a reason to break backwards compatibility at the bit code level for this release, I don't see a compelling reason to bump the major version number to 4.0. As such, I would expect that the next release would be 3.10.</div></div></div></div></div></blockquote><div><br class=""></div></div>To clarify my point: I don't have a particular opinion about bumping the major number for whatever other reason than breaking the compatibility, but I'd probably suggest that we rewrite the compatibility policy to say something like "The current LLVM version support loading any bitcode since version 3.0".<div class=""><br class=""><div class=""><br class=""></div><div class="">-- </div><div class="">Mehdi<br class=""><div class=""><br class=""></div></div></div></body></html>