Halide bug?

rfactor_split.cpp

// g++ rfactor_split.cpp -I ${HALIDE_DIR}/include -I ${HALIDE_DIR}/tools -L ${HALIDE_DIR}/bin -lHalide -o rfactor_split -std=c++11 -O2
// LD_LIBRARY_PATH=${HALIDE_DIR}/bin ./rfactor_split
#include "Halide.h"

using namespace Halide;

int main(int argc, char *argv[]) {
    Var x("x");

    int n = 10000;
    Buffer<float> input(n);

    RDom r(0, n);
    Func f("f");
    f() += input(r);
    RVar rxo, rxi, ryi;
    int tile_width = 32;
    f.update(0)
     .split(r, rxo, rxi, tile_width, TailStrategy::GuardWithIf);
    
    // Adding the rfactor schedule makes f's access out of bound
    // Removing the following 3 lines eliminates the out of bound access
    Var xo;
    Func f_interm = f.update(0).rfactor(rxo, xo);
    f_interm.compute_root();

    Buffer<float> f_buf = Buffer<float>::make_scalar();
    f.realize(f_buf);
    // Error:
    // Input buffer b0 is accessed at 10015, which is beyond the max (9999) in dimension 0

    return 0;
}