A better approach might be to add a flag to gcc to use a different
	CPU description file (one that does not include the bugged
	instructions :)

		David/absolute

             -=-  Sue me, screw me, walk right through me  -=-

On Thu, 17 Dec 1998, Andrew Coles wrote:

> I've thought of a way of working around the StrongARM bug problem, which
> unfortunately involves recompiling, but luckily requires little effort on
> my part (I learnt C last weekend :-)
> 
> If you take the ready-to-be-assembled output from the C compiler (gcc -S)
> you just do an intelligent search-and-replace on the code replacing all the
> bugged instructions (one involving STMIA and another one involving LDR
> AFAIR) with replacement instructions which do the same job, for example,
> unrolling STMs and replacing them with STRs, and then assemble the code
> using the normal 'as' the resultant code is SA bug free.
> 
> All I need to know is what instructions are bugged and need replacing.
> 
> Thanks for any help
> 
> Andrew
>