Hi,

I've been busy with other things, but I'm going to try to get this
done this weekend.

I've also started getting some work on GDB done, and I'm trying to get
that in a semi-decent state before I commit this.  If anyone objects
to that, let me know.

Also, do I use svn+ssh to push into the svn repo?  Are there some docs
on this somewhere? :)

-Pete

On Wed, Mar 7, 2012 at 9:31 PM, Jeremy Bennett
<[email protected]> wrote:
> On Tue, 2012-02-28 at 15:25 +0100, Peter Gavin wrote:
>> Hello,
>>
>> As you might know from seeing me around on IRC, I've been working on
>> bringing the OpenRISC toolchain up to date with the most recent
>> upstream versions.  I've also completed the work that Julius has been
>> doing with binutils to make it use CGEN.  I've also changed the name
>> of the architecture to or1k (from the old or32).  Things seem to be
>> working pretty well, so I figured I'd do a pseudo-announcement on the
>> list so people can give them a try.
>
> Hi Pete,
>
> I've created a new directory for the development tool chain, which can
> mirror FSF mainline.
>
>        http://opencores.org/ocsvn/openrisc/openrisc/trunk/gnu-dev
>
> In there are sub-trees or1k-gcc (for the GCC mirror) and or1k-src (for
> everything else). I've put a snapshot of GCC mainline in or1k-gcc, on
> which you can overlay your changes. or1k-src is empty, so you can
> install your tree, including the SVN files to facilitate upstream
> merging.
>
> The tree is tagged at
>
>        
> http://opencores.org/ocsvn/openrisc/openrisc/tags/gnu-dev/fsf-gcc-snapshot-1-mar-12
>
> I suggest you make a starting tag once you have your changes merged in.
>
> You will have noticed that GCC 4.8 stage 1 has just opened, but with a
> request for a period of stability while 4.7.0 release beds down. So now
> is a really good time to be syncing with mainline.
>
> Best wishes,
>
>
> Jeremy
>
>
> --
> 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
_______________________________________________
OpenRISC mailing list
[email protected]
http://lists.openrisc.net/listinfo/openrisc

Reply via email to