search for: milkymist

...a LatticeMico32 backend in LLVM? LatticeMico32 [1] is an open source microprocessor core designed by Lattice Semiconductor and typically used in FPGAs. It is comparable to the Microblaze processor that you already support. It is already supported by GNU Binutils and GCC (4.5+). It is used by the Milkymist [2] and RTEMS [3] projects. The Milkymist project would like to use the LLVM compiler toolchain as an alternative to GCC, which requires developing a LM32 backend. Thanks, Sébastien Bourdeauducq [1] http://www.latticesemi.com/mico32 [2] http://www.milkymist.org [3] http://www.rtems.org

...t; > LatticeMico32 [1] is an open source microprocessor core designed by Lattice > Semiconductor and typically used in FPGAs. It is comparable to the > Microblaze processor that you already support. > > It is already supported by GNU Binutils and GCC (4.5+). It is used by the > Milkymist [2] and RTEMS [3] projects. The Milkymist project would like to > use the LLVM compiler toolchain as an alternative to GCC, which requires > developing a LM32 backend. > > Thanks, > Sébastien Bourdeauducq > > [1] http://www.latticesemi.com/mico32 > [2] http://www.milkymi...

...o32 [1] is an open source microprocessor core designed by Lattice >> Semiconductor and typically used in FPGAs. It is comparable to the >>  Microblaze processor that you already support. >> >> It is already supported by GNU Binutils and GCC (4.5+). It is used by the >> Milkymist [2] and RTEMS [3] projects. The Milkymist project would like to >>  use the LLVM compiler toolchain as an alternative to GCC, which requires >>  developing a LM32 backend. >> >> Thanks, >> Sébastien Bourdeauducq >> >> [1] http://www.latticesemi.com/mico32 &...

...> parallel, vrtcon, etc) that are added; OTOH, we always use -nodefaults > so those are not added, so at least there should be no difference from > this p.o.v. > > The other changes related to the use of nographics are in few target- > related places: > - in lm32 hardware (milkymist-tmu2), no display device is created when > the display type is "nographics" (but it is when the type is "none"? > hmm..) > - in nvram support, the FW_CFG_NOGRAPHIC bit is set to 1 if the display > is "nographics", while 0 otherwise > - in sparc (no...

...added; OTOH, we always use > > -nodefaults so those are not added, so at least there should be no > > difference from this p.o.v. > > > > The other changes related to the use of nographics are in few > > target- > > related places: > > - in lm32 hardware (milkymist-tmu2), no display device is created > > when> > > the display type is "nographics" (but it is when the type is > > "none"? > > hmm..) > > > > - in nvram support, the FW_CFG_NOGRAPHIC bit is set to 1 if the > > display> &gt...

folks hi, something i just wanted to double-check. is it possible to use, with LLVM, entirely free software tools to build and upload to a xilinx microblaze FPGA target? i take some c code, put it through llvm-fpga, aaand... then what? is there any documentation about this stuff, anywhere? tia, l.

...hw/highbank.c | 10 ++-- hw/integratorcp.c | 10 ++-- hw/kzm.c | 10 ++-- hw/leon3.c | 10 ++-- hw/lm32_boards.c | 18 +++--- hw/mainstone.c | 10 ++-- hw/mcf5208.c | 8 +-- hw/milkymist.c | 10 ++-- hw/mips_fulong2e.c | 9 ++- hw/mips_jazz.c | 14 ++--- hw/mips_malta.c | 10 ++-- hw/mips_mipssim.c | 10 ++-- hw/mips_r4k.c | 10 ++-- hw/musicpal.c | 9 +-- hw/nseries.c...