RFC: Obsoleting or32

[Joel Sherrill <joel@OARcorp.com>]

Ralf Corsepius wrote:
> On Mon, 2005-04-25 at 11:58 +0300, Puro Markku wrote:
> 
>>OpenRISC1000/1200 is quite active.
>>http://www.opencores.org/pnews.cgi/list/or1k?no_loop=yes
>>
>>There is also "OpenRISC 1000 RTEMS"
>>http://www.opencores.org/projects.cgi/web/or1k/rtems
>>
>>BTW: They have weekly builds for GNU Toolchain and OS ports???
>>"The OpenRISC automated testing system (ATS) is, at present, 
>>a single machine which weekly builds OpenRISC GNU Toolchain and 
>>OS ports and reports building problems to the developers."
>>http://www.opencores.org/projects.cgi/web/or1k/ats
> 
> Well, meanwhile, the or32 is gone from RTEMS source-tree, and I don't
> see much reason to resurrect it unless OpenCores changes its policy.
> 
> They are pretty clear they want to do everything themselves -- nothing
> on Earth prevents them from doing so, they forked away from binutils,
> gcc and now are being forked away from RTEMS.

Maintaining a port that does not work to keep their GNU tools ports
up to date in the main source tree is painful.  I haven't had a
complete ORxx toolset in ages.

> I intentionally set a one week deadline, ...

I think it would take a commitment to getting their modifications into
the various GNU tools and working within the system.  having patches to
officially released versions is one thing, forking is another.

Nothing personal.  We have been following the lead of the GNU tools.  If
the support isn't there, we drop the port.

> Ralf

--joel