On Sun, Mar 9, 2014 at 4:48 PM, Jeremy Bennett <[email protected]> wrote: > > Thanks for the info. This seems a compelling reason to just have or1k > and dropping or1knd. > I don't agree. You would have to explicitly do something like ./configure --target=or1k-linux CFLAGS='-mno-delay' for every package you would build. I think having a compiler with sensible defaults is the way to go. If you're developing for a or1k variant without delay slots the default output wouldn't even run. _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
- [OpenRISC] or1knd? (was: Re: [Openrisc] Patching confi... Geert Uytterhoeven
- Re: [OpenRISC] or1knd? (was: Re: [Openrisc] Patch... Christian Svensson
- Re: [OpenRISC] or1knd? (was: Re: [Openrisc] P... Jeremy Bennett
- Re: [OpenRISC] or1knd? (was: Re: [Openris... Christian Svensson
- Re: [OpenRISC] [Openrisc] or1knd? (wa... Christian Svensson
- Re: [OpenRISC] or1knd? (was: Re: [Ope... Peter Gavin
- Re: [OpenRISC] or1knd? (was: Re:... Jeremy Bennett
- Re: [OpenRISC] or1knd? (was:... Christian Svensson
- Re: [OpenRISC] or1knd? (... Peter Gavin
- Re: [OpenRISC] [Openrisc... Stefan Kristiansson
- Re: [OpenRISC] or1knd? (... Jeremy Bennett
