> A quick grep of the arm backend shows 11 instances of reload_in_progress: > > arm.c: && !(reload_in_progress || reload_completed) > arm.c: if (! (reload_in_progress || reload_completed) > arm.c: if (! (reload_in_progress || reload_completed) > arm.c: if (! (reload_in_progress || reload_completed) > arm.c: reload_in_progress || reload_completed)) > arm.md: "TARGET_32BIT && (reload_in_progress || reload_completed)" > arm.md: "TARGET_32BIT && (reload_in_progress || reload_completed)" > arm.md: "TARGET_32BIT && (reload_in_progress || reload_completed)" > arm.md: "TARGET_32BIT && (reload_in_progress || reload_completed)" > predicates.md: "offsettable_address_p (reload_completed | > reload_in_progress, > predicates.md: (and (match_test "reload_in_progress || > reload_completed") > > and aarch64 has five more: > > aarch64.md: "reload_completed || reload_in_progress" > aarch64.md: "reload_completed || reload_in_progress" > aarch64.md: "reload_completed || reload_in_progress" > aarch64.md: "reload_completed || reload_in_progress" > aarch64.md: "reload_completed || reload_in_progress" > > Yvan, could you do a quick audit on these to see if they are also likely > to need fixing?
Yes, I'll check all of them.
