Currently the schedule_program implementation being used is picked
at compile time, which on the Android platform means that the
bifrost compiler & scheduler is used for all targets, including
midgard based hardware.
This commit disambiguates between the two schedule_program functions.
Signed-off-by: Robert Foss <robert.foss@collabora.com>
Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
}
} while (progress);
- schedule_program(ctx);
+ bifrost_schedule_program(ctx);
#ifdef BI_DEBUG
nir_print_shader(nir, stdout);
}
-void schedule_program(compiler_context *ctx)
+void bifrost_schedule_program(compiler_context *ctx)
{
// XXX: we should move instructions together before RA that can feed in to each other and be scheduled in the same clause
allocate_registers(ctx);
#define bifrost_ra_h
#include "compiler_defines.h"
-void schedule_program(compiler_context *ctx);
+void bifrost_schedule_program(compiler_context *ctx);
#endif /* bifrost_ra_h */
/* Scheduling */
-void schedule_program(compiler_context *ctx);
+void midgard_schedule_program(compiler_context *ctx);
void mir_ra(compiler_context *ctx);
void mir_squeeze_index(compiler_context *ctx);
mir_add_writeout_loops(ctx);
/* Schedule! */
- schedule_program(ctx);
+ midgard_schedule_program(ctx);
mir_ra(ctx);
/* Now that all the bundles are scheduled and we can calculate block
}
void
-schedule_program(compiler_context *ctx)
+midgard_schedule_program(compiler_context *ctx)
{
midgard_promote_uniforms(ctx);