Difference in JIT and AOT schedulling

[Doubl3MD]

With this schedule :

   main
      .tile(x, y, x_outer, y_outer, x_inner, y_inner, 64, 64)
      .fuse(x_outer, y_outer, tile_index)
      .parallel(tile_index);
   Var x_inner_outer, y_inner_outer, x_vectors, y_pairs;
   main
      .tile(x_inner, y_inner, x_inner_outer, y_inner_outer, x_vectors, y_pairs, 4, 2)
      .vectorize(x_vectors)
      .unroll(y_pairs);

When I JIT compile for testing over an image with size smaller than the tile size of 64,64 it passes.
When I AOT and use the function call on the same image I get an error(crash and burn).

It's logic, I guess, that it doesn't work when the tile size is bigger than the full image size, but I would expect that with JIT it would produce a similar error, which it doesn't.

I'm just looking for the logical explanation why or why not... so, anybody? :)

[abadams]

JIT mode checks to see if the output is too small, and if so computes a bigger output and returns a crop of it.

[steven-johnson]

I suspect that using JIT mode with compile_to_callable(), rather than realize(), would likely mimic AOT behavior exactly.

[soufianekhiat]

Reference for similar issue:
#5915