[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[creduce-bugs] Assertion `RWBuf && "Empty RewriteBuffer!"' failed
- Subject: [creduce-bugs] Assertion `RWBuf && "Empty RewriteBuffer!"' failed
- From: eeide at cs.utah.edu (Eric Eide)
- Date: Tue, 26 Nov 2013 08:30:04 -0700
- In-reply-to: <U+0414><U+043C><U+0438><U+0442><U+0440><U+0438><U+0439> <U+0414><U+044C><U+044F><U+0447><U+0435><U+043D><U+043A><U+043E>'s message of Tuesday, November 26 2013 <CADJjh6m=ebkq=UJEFLqpLL_Lvx-GdTzW8mX65iUxuj51votnKA@mail.gmail.com>
- References: <CADJjh6mPWZSRKM3FcEKs_BrSYDzgLoecy89mWvaJxqkywP4W0Q@mail.gmail.com> <52907940.7080707@cs.utah.edu> <CADJjh6m=ebkq=UJEFLqpLL_Lvx-GdTzW8mX65iUxuj51votnKA@mail.gmail.com>
> Sorry, I was inprecise -- I use branch llvm-svn-compatible and sound
> like with llvm-current + creduce-llvm-svn-compatible-current
> crash is not fixed :(
tl;dr Yang will probably merge the fix into the llvm-svm-compatible branch
ASAP.
Longer: We (Utah) don't currently have a very precise policy about when we
propagate work from the master branch to the llvm-svn-compatible branch. The
llvm-svn-compatible branch is, after all, about collecting LLVM compatibility
fixes, not about collecting general fixes/improvements. Nevertheless, we
currently *do* merge master into llvm-svn-compatible from time to time.
You can do this yourself, of course, in any clone you make. Just:
git clone ...
git checkout llvm-svn-compatible
git merge master
Given that it is easy for people to do the merge if they want it, I might try
to convince John and Yang that we should *stop* doing the merges except at LLVM
release points. But I expect that I will not be able to persuade them :-).
Eric.
--
-------------------------------------------------------------------------------
Eric Eide <eeide at cs.utah.edu> . University of Utah School of Computing
http://www.cs.utah.edu/~eeide/ . +1 (801) 585-5512 voice, +1 (801) 581-5843 FAX