https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103383
--- Comment #1 from Rich <rkujoth at motorolasolutions dot com> --- Seems like I probably misunderstood the meaning of "TARGET_REORDER" -- looks like it's a Microblaze build option and this keyword appears to be there to indicate that these instructions only exist with a certain set of build options (which are the default). So, perhaps the issue I'm seeing is a bit more generic? How does GCC perform the delayed branch optimization? If an operation requires multiple instructions, how does GCC know not to stick it in the branch delay slot?
