gcc 4.x status for RTEMS
ralf.corsepius at rtems.org
Thu Jan 27 17:18:32 UTC 2005
On Thu, 2005-01-27 at 09:59 -0600, Joel Sherrill wrote:
> I woudl like to get everyone to review the gcc 4.x tool status
> notes on the Wiki and make sure their favorite GCC PR is covered.
> I have been trying to track the issues but have a feeling I am
> missing something.
> AFAIK The worst problems left are:
> + various m68k internal compiler errors building RTEMS. I am unsure
> if all of these are listed on the Wiki.
+ ditto for the avr.
> + Cross gnat tools do not build. There is a Makefile issue.
Even if you should manage to solve this issue, then there remains the
GNAT not supporting multilibs. IMO, this basically leaves GNAT the same
shape as it has been with gcc-3.x: pretty much useless.
> + tic4x doesn't build.
> Peter Barada has offered to look into our m68k issues so let's make
> sure all of them are reported with testcases he can try to reproduce
> on m68k-elf or m68k-linux. Doing so increases the likelihood of them
> being fixed in a timely manner.
> My current gcc CVS source tree has modifications to the following files:
> M gcc/hard-reg-set.h
This patch is obsolete. Joern checked in a replacement a couple of days
ago (cf. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19528)
> M gcc/config/arm/rtems-elf.h
> M gcc/config/c4x/rtems.h
> M gcc/config/i386/t-rtems-i386
+ The sparc/t-rtems (LINK_GCC_C_SEQUENCE_SPEC) patch is missing.
Bernardo's recent patch did not fix this issue. I have a local patch
pending, but have not yet tested it with current GCC-4.0.
+ I still need to resolve the sh-multilib issue.
> Ralf.. I think it is safe to commit the bottom 3 and I am unsure if this
> patch still applies.
No problem - I have these, rsp. my current versions, in a local CVS.
More information about the users