Go to file
Stafford Horne fa8b7c2128 sim: or1k: add or1k target to sim
This adds the OpenRISC 32-bit sim target.  The OpenRISC sim is a CGEN
based sim so the bulk of the code is generated from the .cpu files by
CGEN.  The engine decode and execute logic in mloop uses scache with
pseudo-basic-block extraction and supports both full and fast (switch)
modes.

The sim does not implement an mmu at the moment.  The sim does implement
fpu instructions via the common sim-fpu implementation.

sim/ChangeLog:

2017-12-12  Stafford Horne  <shorne@gmail.com>
	    Peter Gavin  <pgavin@gmail.com>

	* configure.tgt: Add or1k sim.
	* or1k/README: New file.
	* or1k/Makefile.in: New file.
	* or1k/configure.ac: New file.
	* or1k/mloop.in: New file.
	* or1k/or1k-sim.h: New file.
	* or1k/or1k.c: New file.
	* or1k/sim-if.c: New file.
	* or1k/sim-main.h: New file.
	* or1k/traps.c: New file.
2017-12-12 23:44:14 +09:00
bfd Automatic date update in version.in 2017-12-12 00:00:33 +00:00
binutils [Binutils][Objdump]Check symbol section information while search a mapping symbol backward. 2017-12-11 15:42:47 +00:00
config
cpu
elfcpp
etc
gas Don't mask X_add_number containing a register number 2017-12-12 11:03:58 +10:30
gdb gdb: testsuite: Add or1k tdesc-regs.exp test support 2017-12-12 23:38:31 +09:00
gold Add plugin API for processing plugin-added input files 2017-12-11 14:58:38 -08:00
gprof Support --localedir, --datarootdir and --datadir 2017-11-29 20:10:52 +10:30
include Add plugin API for processing plugin-added input files 2017-12-11 14:58:38 -08:00
intl
ld Objcopy interleave test 2017-12-07 23:04:15 +10:30
libdecnumber
libiberty
opcodes [Binutils][Objdump]Check symbol section information while search a mapping symbol backward. 2017-12-11 15:42:47 +00:00
readline
sim sim: or1k: add or1k target to sim 2017-12-12 23:44:14 +09:00
texinfo
zlib
.cvsignore
.gitattributes
.gitignore
ChangeLog Add gdb for or1k build 2017-12-12 23:39:28 +09:00
compile
config-ml.in
config.guess
config.rpath
config.sub
configure Add gdb for or1k build 2017-12-12 23:39:28 +09:00
configure.ac Add gdb for or1k build 2017-12-12 23:39:28 +09:00
COPYING
COPYING3
COPYING3.LIB
COPYING.LIB
COPYING.LIBGLOSS
COPYING.NEWLIB
depcomp
djunpack.bat
install-sh
libtool.m4
lt~obsolete.m4
ltgcc.m4
ltmain.sh
ltoptions.m4
ltsugar.m4
ltversion.m4
MAINTAINERS
Makefile.def
Makefile.in
Makefile.tpl
makefile.vms
missing
mkdep
mkinstalldirs
move-if-change
README
README-maintainer-mode
setup.com
src-release.sh
symlink-tree
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.

If you are receiving this as part of a GDB release, see the file gdb/README.
If with a binutils release, see binutils/README;  if with a libg++ release,
see libg++/README, etc.  That'll give you info about this
package -- supported targets, how to use it, how to report bugs, etc.

It is now possible to automatically configure and build a variety of
tools with one command.  To build all of the tools contained herein,
run the ``configure'' script here, e.g.:

	./configure 
	make

To install them (by default in /usr/local/bin, /usr/local/lib, etc),
then do:
	make install

(If the configure script can't determine your type of computer, give it
the name as an argument, for instance ``./configure sun4''.  You can
use the script ``config.sub'' to test whether a name is recognized; if
it is, config.sub translates it to a triplet specifying CPU, vendor,
and OS.)

If you have more than one compiler on your system, it is often best to
explicitly set CC in the environment before running configure, and to
also set CC when running make.  For example (assuming sh/bash/ksh):

	CC=gcc ./configure
	make

A similar example using csh:

	setenv CC gcc
	./configure
	make

Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.