> > Sometimes you don't care whether you do only "half" a macro instruction > > if the branch is taken. Usually though, the warning is a good thing - I > > remember having spent many hours finding bugs like this with assemblers > > that don't issue warnings. > > This is exactly what ".set nomacro" is for -- I can't see any reason for > such warnings when ".set macro" is active. While in general I like playing with sharp knives (you should see my cluster admin toolkit), and I like my kernel to run fast, and the only thing that gets trashed is usually at, I still think I'd prefer to have nops in those delay slots in the kernel. Hand-written assembly is unlikely to use ".set nomacro" properly. -- greg
