1/1 
|
Re: [openrisc] opcodes/or32-opc.c
by Unknown on Mar 12, 2004 |
Not available! | ||
|
Hi !
Want thing I want to mention. Files shared between or1ksim, binutils, gcc
and gdb that have the same content (I think or32.c and soem others) are sym
linked in the cvs. That means if you update anyone of these files, all other
gets updated. These are called "CVS links" and are done with the "CVS links"
tool on opencores.
It is important whenever you add or import new version of gcc for example,
to recreate these cvs sym links with the cvs links tool. This way you only
have to update or32.c and other files in one of the toolchain part and it
gets automatically updated elsewhere.
To see all active cvs links and to create/remove links:
http://www.opencores.org/cvslinks.cgi
For example I have noticed that the latest gcc-3.2.3 doesn't have a link to
or32.c.
regards,
Damjan
PS Because cvs links is a universally useful tool since it can also link any
cvs "module" into hierarchy of a different module I send this emaqil to the
cores list as well. For example, the orp_soc in or1k/orp/orp_soc is done in
this way - in links all the cores to form this soc simply with cvs links.
----- Original Message -----
From: "Johan Rydberg" jrydberg at night.trouble.net>
To: openrisc at opencores.org>
Sent: Thursday, March 11, 2004 2:01 AM
Subject: [openrisc] opcodes/or32-opc.c
Hi.
Is there currently being any code shared between for example the simulator and opcodes in binutils? I'm thinking about cleaning it up a bit, maybe but the functions in another
namespace (right now they are prefixed with simply insn_, which is a bit
too
generic for my taste.) -- there seem also to be a bit of code duplication
between or32-opc.c, or32-dis.c and GAS.
--
Johan Rydberg, Free Software Developer, Sweden
http://rtmk.sf.net | http://www.nongnu.org/guss/
Playing Incubus - Just A Phase
_______________________________________________
http://www.opencores.org/mailman/listinfo/openrisc
|
|||
1/1