[linuxsh-dev] stable SH4 environment

[kaz K. <kk...@rr...>]

NIIBE Yutaka <gn...@m1...> wrote:
>> 4) what is an approximate timeframe for getting binutils and gcc patches
>> for LinuxSH merged with the mainline GNU trees? My work with Linux
>> on the PPC405 has led me to think that this should be a _really_ high
>> priority for all embedded forks of Linux/GNU tools. If my employer
>> allows, I could be able to spend some time assisting in what ever way
>> possible.
>> 
>> Thanks! I'm looking forward to working with all of you again.
> 
> Yes, I think so too.  I'm not sure for the timeframe, I expects Kaz
> comments for that.  I explain the current status here.

I also have no clear plan. Anyway, almost essential changes are already
included in mainline except a few patches. Some unsended patches need
more tests, for example, like -mno-fdiv-divsi patch.

> This two weeks, I've tried to provide GNU/SH tool-chain for Debian.
> I've done some work based on binutils-2.11.2 and GCC 3.0.1.
> 
> I think that binutils is ready for use.  I sent diffs to Takeshi for
> comments.  I expect new binutils-sh-linux Debian package comes soon by
> Takeshi.  And I sent the needed diff to Kaz for comments, then, he
> tried it to current CVS version.  Next comes, send them to mainline
> binutils development.

I'm putting patches for the current CVS as

  http://dodo.nurs.or.jp/~kkojima/gnu-on-sh/src-cvs-010822.diff
  http://dodo.nurs.or.jp/~kkojima/gnu-on-sh/src-cvs-010822-2add.tar.gz

I'm happy if you have time to test this.

> For GCC, I think that it's not ready.  Major concern is the definition
> of multilibbed environment.  I built my own Debian gcc-sh-linux 3.0.1
> package.  I'm now using this for my experiment, and try to build some
> sort of Debian SH-4 distribution with this 3.0.1.  While I'm doing
> this week, I encountered issues of name of libgcc shared library, 
> still not solved.

I think so. Shared libgcc of 3.x is a drastic change and is a kind of
"no return".

	kaz