"Richard Earnshaw (lists)" writes:
> On 17/09/2019 15:57, Richard Sandiford wrote:
>> no_insn is documented as:
>>
>>an insn which does not represent an instruction in the final output,
>>thus having no impact on scheduling.
>>
>> and is used in that way by the arm port (e.g. for define_
On 17/09/2019 15:57, Richard Sandiford wrote:
no_insn is documented as:
an insn which does not represent an instruction in the final output,
thus having no impact on scheduling.
and is used in that way by the arm port (e.g. for define_insns that
expand to comments). However, most schedul
no_insn is documented as:
an insn which does not represent an instruction in the final output,
thus having no impact on scheduling.
and is used in that way by the arm port (e.g. for define_insns that
expand to comments). However, most scheduling descriptions instead
assigned units to no_insn
