gcc 4.x status for RTEMS

Joel Sherrill <joel@OARcorp.com> joel.sherrill at OARcorp.com
Thu Jan 27 15:59:19 UTC 2005


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.
+ Cross gnat tools do not build.  There is a Makefile issue.
+ 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
M gcc/config/arm/rtems-elf.h
M gcc/config/c4x/rtems.h
M gcc/config/i386/t-rtems-i386

Ralf.. I think it is safe to commit the bottom 3 and I am unsure if this
patch still applies.

Index: gcc/hard-reg-set.h
RCS file: /cvs/gcc/gcc/gcc/hard-reg-set.h,v
retrieving revision 1.25
diff -u -r1.25 hard-reg-set.h
--- gcc/hard-reg-set.h	15 Jan 2005 16:06:14 -0000	1.25
+++ gcc/hard-reg-set.h	27 Jan 2005 15:57:47 -0000
@@ -499,4 +499,19 @@

+/* Determine if two hard register sets intersect.
+   Return 1 if they do.  */
+static inline bool
+hard_regs_intersect_p (HARD_REG_SET *a, HARD_REG_SET *b)
+  COPY_HARD_REG_SET (c, *a);
+  AND_HARD_REG_SET (c, *b);
+  GO_IF_HARD_REG_SUBSET (c, reg_class_contents[(int) NO_REGS], lose);
+  return 1;
+  return 0;


More information about the users mailing list