This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
So confused
- From: "Brett Beebe" <beebeb at comcast dot net>
- To: <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 21 Jun 2004 08:28:21 -0700
- Subject: So confused
Hello,
I am trying to bring the port for m68k palmos upto date with gcc version
3.3. First I started by looking at the changes made to gcc version 2.95.x.
That's when I noticed that the attribute system between 2.95 and 3.3 are
completely different. I scratched my head, and started to search the
internet for more information, I have found a lot of information that will
require a lot of reading. So I went back to the drawing board.
I compiled a cross compiler for the m68k-elf target. That was pretty easy
once I found the proper information. I then compiled a test program I had
from gcc version 2.95 to see what real changes there was. The biggest
change was to call PalmOs functions requires a 'trap' instead of a 'bsr'.
So right now I still have several options. I can modify gcc to produce a
'trap' instruction for calls to PalmOs or I can produce a PalmOs library,
that would have all of the correct calls in it. So, for whatever reason I
decided to modify the gcc code. I did a grep for 'bsr' in binutils and the
gcc code. In binutils/m68k-opc.c I generated a patch to replace all 'bsr'
instruction with 'nop'. To try an understand what I needed to do. Well
binutils compiles ok, but gcc-core no longer compiles. So I threw out that
patch. I generated a patch for gcc/m68k.md to replace all define_inst for
"jump" or that use 'bsr' with a nop. At this point binutils/gcc-core/and
gcc-3.3.1 all compile. The patch is only placed into gcc-3.3.1 not
gcc-core. When I look at the assembly listing of my file I still see 'bsr'
instructions.
So could someone please tell we what I am doing wrong? I am sooo confused.
Thanks.