On 10/22/12, R. Diez <[email protected]> wrote: > >> Regarding the delay slot coding, why don't you mention the > >> availability of the macros in the or1k-asm.h header > > I was trying to encourage writing a single binary that runs on CPUs with and > without jump delay slots, and those macros don't allow you to do that. > Furthermore, they make the code a little uglier. But I'll mention them > anyway.
Well, you write code and compile a binary. If you're wanting to compile a binary which will run on both, fine, you should never put anything other than a l.nop in the delay slot. But if you're going to write code to be compatible with both I would encourage the use of the macros in or1k-asm.h. Thanks for mentioning it in your documentation. I can't think of any or1k apps you would distribute as binary, though. Being a highly configurable embedded platform, everyone will be compiling with their own binaries according to a configuration to suite their needs. You're also discarding one of the benefits of discarding the delay slot which is reduced code size (All the l.nops filling delay slots because the compiler couldn't find anything good to put there.) Cheers Julius _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
