[llvm-bugs] [Bug 3082] loop-extractor infinite memory usage

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Feb 3 17:44:37 PST 2017


https://llvm.org/bugs/show_bug.cgi?id=3082

Nick Lewycky <nlewycky at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #3 from Nick Lewycky <nlewycky at google.com> ---
The .bc format has changed incompatibly since this bug was filed. I don't care
enough to bother finding an llvm 2.5 / 2.6 series compiler to llvm-dis and
upgrade it. It's unlikely the same bitcode will still trigger the same bug,
even if the underlying bug is still unfixed. Closing WONTFIX.


One other thing. "748bc4973cbfe2bac372bd83fb814618e4fc3d9c" isn't a revision
number. LLVM is, for now, still hosted on svn and we use svn revision numbers
as a project. Even when LLVM does go to git, the plan is to use a monotonically
increasing number because those are so valuable.
http://llvm.org/docs/Proposals/GitHubMove.html#on-managing-revision-numbers-with-git

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170204/55e28fa4/attachment-0001.html>


More information about the llvm-bugs mailing list