On Sun, 2012-05-27 at 10:44 +0200, Olof Kindgren wrote:
> 
> 
> 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.

<p>
Hi Olof
</p>
<p>
Your analysis is spot on. We discussed this, when we met last July. The
architecture name should not include the bus width of one specific
implementation.
</p>
<p>
This chops and changes every few years. We had or1k as the architecture
name in GDB for many years, but that was changed to or32 to match all
the other tools. Some of the GNU tool chain was contributed upstream
under the name "openrisc", but the architecture is OpenRISC 1000, and we
already know that the proposed OpenRISC 2000 will be an incompatible
(forwards and backwards) architecture.
</p>
<p>
So let us stick with or1k. It is what all the new work (Peter Gavin on
GNU tools, Stefan Kristiansson/Julius Baxter on LLVM is using). Part of
this work is the extremely tedious slog of changing all the
infrastructure references from or32 to or1k. Welcome to the real world
of tool chains.
</p>
<p>
Jeremy
</p>

BTW - could the openrisc.net/openrisc.org admins check their list
mailers - I'm not getting all the messages in these discussions which
makes them difficult to follow.

-- 
Tel:      +44 (1590) 610184
Cell:     +44 (7970) 676050
SkypeID: jeremybennett
Email:   [email protected]
Web:     www.embecosm.com

_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to