I have no idea who to ask so I'd like to ask you, if you don't mind.
The following bug has gnu as(1) implications because it does not handle
the errata below at all.
I REALLY need information on the '-t5_nops_follow_br' for the
It helps me with a bug in gcc-2.92.2 but I need to know if it does
anything else (details below).
Please feel free to forward this to anyone who might help.
The key background information is that some mips processors have a bug
whereby a 64-bit shift after a 64-bit divide can cause the shift to
produce an incorrect result.
This is a known problem and the errata can be found on:
#28 on page 7
The mips/sgi assembler will cover for this by adding a nop
between a divide and a subsequent shift.
However, depending on how gcc is invoked (debug optimization) when it
generates this sequence it may insert a lable between the divide and
the shift. The IRIX assembler no longer recognizes the sequence and
does not insert the the nop.
If we pass the IRIX assembler the '-t5_nops_follow_br' it solves the
problem forcing the nop and actually it results in two, which if
unrestricted could result in some serious performance issues.
We would like to know what else it will do to our other code, it seems
harmless, but we would like to know specifics if they are available.
here is a code sample with the label, remove the label and IRIX as(1)
insterts the nop, gnu as(1) does not.