#
66c13fd4 |
|
15-Jan-2019 |
Andrew Waterman <aswaterman@gmail.com> |
Revert "Don't require a RISC-V libc and crt when configuring (#132)" (#140) This reverts commit a02257a861a4d13f31868a27c197cfc5576101e1.
|
#
a02257a8 |
|
04-Jan-2019 |
James Clarke <jrtc27@jrtc27.com> |
Don't require a RISC-V libc and crt when configuring (#132)
|
#
00f0dd04 |
|
26-Jul-2018 |
Zong Li <zong@andestech.com> |
Fix stubs-lp64.h/stubs-lp64d.h/stubs-ilp32.h/stubs-ilp32d.h not found For now, we always compile files with -mabi option by using soft-fp ABI. But there are some files use the header which in toolchain, like unistd.h, stdint.h and so on. Finally, these header files include other header files which existing depend on ABI such as stubs-lp64.h or stubs-lp64d.h. So it causes the header file not found when using the double-float toolchain with soft-float ABI. Fix up by compiling files with -march and -mabi options only if there is specifying the --with-arch option at configure time. If use the --with-arch option at configure time, that means your toolchain has multi-lib support, so always building riscv-pk by soft-float ABI is fine. Otherwise, we don't compile files with specifying march and mabi options explicitly
|
#
16476bd8 |
|
09-Jul-2018 |
Andrew Waterman <andrew@sifive.com> |
Properly license all nontrivial files
|
#
c3cf29a8 |
|
30-Apr-2018 |
Zong Li <zong@andestech.com> |
Replace the --enable-32bit option by --with-arch Get rid of the --enable-32bit option and switch to use --with-arch, which is more standard because it matches the GCC build. If --with-arch is not specified, it defaults to whatever the compiler's default is. The --with-abi is not necessary for this project. Unconditionally compile it with a no-float ABI.
|
#
e22aaec2 |
|
03-Nov-2017 |
Palmer Dabbelt <palmer@dabbelt.com> |
Fix line endings in the logo
|
#
455608b4 |
|
03-Nov-2017 |
Palmer Dabbelt <palmer@dabbelt.com> |
Allow users to pick a logo
|
#
f6bca6e3 |
|
20-Feb-2017 |
Andrew Waterman <andrew@sifive.com> |
Don't block for acks on console writes
|
#
dc939be3 |
|
16-Jul-2016 |
Prashanth Mundkur <prashanth.mundkur@gmail.com> |
Support 32bit build (#27) * Support configuration for a 32-bit build. * Regenerate configure.
|
#
b94c7a4b |
|
10-Mar-2016 |
Andrew Waterman <waterman@cs.berkeley.edu> |
Refactor pk, bbl, machine into separate libraries Yuck.
|
#
25acd5c8 |
|
02-Sep-2015 |
Andrew Waterman <waterman@cs.berkeley.edu> |
Don't automatically run autoconf Run it yourself if you modify configure.ac, and commit the configure script.
|
#
3cf271eb |
|
18-May-2015 |
Palmer Dabbelt <palmer@dabbelt.com> |
Change the behavior of the DESTDIR make variable DESTDIR is a common make idiom. As per the GNU coding standards https://www.gnu.org/prep/standards/html_node/DESTDIR.html "DESTDIR is a variable prepended to each installed target file, like this: $(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo $(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a The DESTDIR variable is specified by the user on the make command line as an absolute file name. For example: make DESTDIR=/tmp/stage install DESTDIR should be supported only in the install* and uninstall* targets, as those are the only targets where it is useful. If your installation step would normally install /usr/local/bin/foo and /usr/local/lib/libfoo.a, then an installation invoked as in the example above would install /tmp/stage/usr/local/bin/foo and /tmp/stage/usr/local/lib/libfoo.a instead." The current Makefile.in uses DESTDIR, but has a slightly non-standard behavior: the target install location doesn't include "$prefix". This breaks package managers, because stuff ends up getting installed to the wrong location. Unfortunately the only way I can think of to fix this involves silently changing the behavior of DESTDIR. Hopefully nobody is using it...? [port of 8a2088b59162fe16c16d26ddc1cfcaaaa8c4156f in riscv-fesvr]
|
#
87683e74 |
|
10-May-2015 |
Andrew Waterman <waterman@cs.berkeley.edu> |
Split pk functionality into pk and bbl pk is now an AEE only (i.e. it can only execute user programs). bbl is now an SEE only (i.e. it can only host kernels).
|
#
fda0d85a |
|
26-Oct-2014 |
Andrew Waterman <waterman@cs.berkeley.edu> |
Don't rely on the C library
|
#
6941d5f6 |
|
30-Aug-2012 |
Christopher Celio <celio@eecs.berkeley.edu> |
respect CFLAGS and LDFLAGS env vars
|
#
0edaecc5 |
|
19-Jun-2011 |
Andrew Waterman <waterman@s141.Millennium.Berkeley.EDU> |
temporary undoing of renaming
|
#
e63e4fbe |
|
19-Jun-2011 |
Andrew Waterman <waterman@s141.Millennium.Berkeley.EDU> |
Renamed packages
|
#
0d603acb |
|
15-Apr-2011 |
Andrew Waterman <waterman@s144.Millennium.Berkeley.EDU> |
[pk] load pk at addr 0; user stack top = MEMSIZE
|
#
664411d5 |
|
02-Nov-2010 |
Andrew Waterman <waterman@s144.Millennium.Berkeley.EDU> |
[opcodes, pk, sim, xcc] made jumps shorter and PC-relative
|
#
b4fd490d |
|
15-Oct-2010 |
Andrew Waterman <waterman@s144.Millennium.Berkeley.EDU> |
[pk, sim] added FPU emulation support to proxy kernel
|
#
29cc0dc9 |
|
18-Aug-2010 |
Andrew Waterman <waterman@s141.Millennium.Berkeley.EDU> |
[pk,fesvr] improved proxykernel build system Now uses a modified MCPPBS. Add --host=riscv to configure path. Front-end server now just searches PATH for riscv-pk, so just install the pk to somewhere in your path.
|