2012/5/27 Julius Baxter <[email protected]> > > By the way, when you announced the change of arquitecture name, I > suspected trouble. And indeed I had to patch my build system all over the > place in order to support both names "or32" and "or1k". I wonder if we > should revert back to "or32" and save further trouble when others start > switching to the new toolchain. > > I'm all for the re-name. It _should_ be as easy as changing the tool > chain prefix in one place in the scripts for a project to implement > such a change. > > Cheers > > Julius > _______________________________________________ > OpenRISC mailing list > [email protected] > http://lists.openrisc.net/listinfo/openrisc >
All for re-naming from what to what? There is some confusion here :) IIRC the renaming (from or1k?) to or32 a few years ago turned out to be a less fortunate decision, and that the new GNU toolchain was a chance to get this right. or1k is really the architecture name, and 32 is the bus width. -- Olof Kindgren ______________________________________________ ORSoC Website: www.orsoc.se Email: [email protected] ______________________________________________ FPGA, ASIC, DSP - embedded SoC design
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
