This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Introducing a nanoMIPS port for GCC
- From: Matthew Fortune <Matthew dot Fortune at mips dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Robert Suchanek <Robert dot Suchanek at mips dot com>, "gcc at gcc dot gnu dot org (gcc at gcc dot gnu dot org)" <gcc at gcc dot gnu dot org>, Toma Tabacu <Toma dot Tabacu at mips dot com>, Zoran Jovanovic <Zoran dot Jo at mips dot com>, Faraz Shahbazker <Faraz dot Shahbazker at mips dot com>, Jack Romo <Jack dot Romo at mips dot com>, Stefan Markovic <Stefan dot Markovic at mips dot com>, Sara Popadic <Sara dot Popadic at mips dot com>
- Date: Wed, 2 May 2018 20:52:37 +0000
- Subject: RE: Introducing a nanoMIPS port for GCC
- References: <9253772adfd3429dbdaddf0dd622c709@mips.com> <alpine.DEB.2.20.1805021515480.21824@digraph.polyomino.org.uk>
Joseph Myers <joseph@codesourcery.com> writes:
> On Wed, 2 May 2018, Matthew Fortune wrote:
>
> > qemu
> > ====
> > http://lists.nongnu.org/archive/html/qemu-devel/2018-05/msg00081.html
>
> That answers one thing I was wondering, by saying you're using the generic
> Linux kernel syscall interface rather than any of the existing MIPS
> syscall interfaces.
>
> Is your Linux kernel port available somewhere (or a description of it
> corresponding to these descriptions of changes to toolchain components)?
Hi Joseph,
The kernel is being prepared for a branch in the linux-mips.org repository
and a document adding to the wiki there. All being well it will not take
too long to get that available.
To my knowledge the major areas of the nanoMIPS kernel that are not yet
finalised are the debug interfaces but our kernel engineers will be able
to give a more detailed description.
Matthew