This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Dear all,this is my first attempt to submit my OpenRISC port which I developed here: https://github.com/wallento/or1k-newlib
Due to the list's message size restrictions I cannot attach the patches:- https://raw.githubusercontent.com/wallento/or1k-newlib/for-upstream-2014-12-10/0001-OpenRISC-Add-no-delay-slot-support.patch
- https://raw.githubusercontent.com/wallento/or1k-newlib/for-upstream-2014-12-10/0002-libgloss-OpenRISC-support.patch
- https://raw.githubusercontent.com/wallento/or1k-newlib/for-upstream-2014-12-10/0003-newlib-OpenRISC-Baremetal-support.patch
The port is based on the never-upstreamed port maintained by the OpenRISC community. This one was unfortunately GPL and I corresponded with all authors in the final port to change the license to BSD.
The port is twofold: A rather large libgloss that contains a lot of baremetal support functions to handle exceptions, interrupts, etc. easily. Beside this, I added a sys folder for the or1k-elf target that uses dynamic reentrancy and depends on libgloss. The machine folder is still compatible with the or1k-rtems toolchain. I am really not sure if this is the way to go, so please comment on other ways.
The port already contains multicore support with a shared heap and private stacks, reentrancy data structures and port internal data structures.
I am looking forward to your feedback and hope the code quality is above your expectations on a guy from academia ;)
Best regards, Stefan
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |