This has been broken since Jed merged his buggy branch into next. It has been reported to Jed repeatedly.
> On Feb 27, 2015, at 6:45 AM, Mark Adams <[email protected]> wrote: > > Jed, I see this in next, but I am puzzled, I tested a week ago (did I forget > to test next?), and I do not see this commit in next, or master, with > SourceTree. > > 07:35 (5ab6ef6...)|BISECTING ~/Codes/petsc$ git bisect good > ee5fc33bea6969d0579ded3dbfac725151deab42 is the first bad commit > commit ee5fc33bea6969d0579ded3dbfac725151deab42 > Author: Jed Brown <[email protected]> > Date: Wed Dec 4 13:00:40 2013 -0700 > > VecAssembly BTS: enable by default, use -vec_assembly_bts 0 to disable > > Note that -vec_assembly_bts can only be disabled if VecSetFromOptions is > called, which it often is not. Hopefully the old stash communication > routines can be deleted soon, and then all the options go away. > > :040000 040000 388f1fa7e4c763cdb65caf22fa1f42970a73a5e7 > 7ccce92e0efa7184c23fe507942d273a1ac89665 M src >
