Is the RISC V source code available to the public (Where is the source code?) [closed] - cpu-architecture

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
I am a student and would like to know where the source code for RISC V is hosted at so I can learn and create my own 'architecture', with credits of course.
And my other question is that if the source code is inaccessible to the community, then how is it considered Open Source?
Thanks

RISC-V is an architecture (https://riscv.org/blog/2020/02/risc-v-is-not-an-open-source-processor-krste-asanovic-chairman-of-the-board-risc-v/) which is open and royalty-free to implement. There are various implementations in VHDL or whatever (microarchitectures), including some open-source ones. google found https://github.com/riscv/riscv-cores-list which lists various designs by license. For example https://opencores.org/projects/biriscv. AFAIK, the fully open-source ones are in-order, not super-wider or OoO exec.
TL:DR: there isn't "the source code" for RISC-V overall.
Unless you mean the LaTeX source for the ISA specification docs (https://riscv.org/technical/specifications/), in which case yes, that page (currently) even links to https://github.com/riscv/riscv-isa-manual/releases/tag/draft-20210805-4e220a3 which has "source code" .tar.gz and .zip links which I assume contain LaTeX or similar source the PDFs are built from.
An architecture / ISA is a paper specification that CPUs implement, and that software is written against. It includes details like instruction encodings, and also memory ordering rules, exception handling, page table formats, etc. All the rules that specify what happens. But none of the internal implementation details.
You can modify that if you want, to customize the architecture e.g. by adding new instructions or new / different semantics for something, because RISC-V is open-source. (And then design CPUs that implement it and write software for them)

Related

Finding Common Lisp Libraries [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm using QuickLisp to load Common Lisp libraries. However, there are many libraries that all do similar things. For example, there are many libraries that all deal with parsing a CSV file.
Are there any resources you use to check which libraries meet your needs? How do you determine if a library is still being supported? Are there any heuristics short of visiting individual libraries's websites?
I'm aware of http://www.cliki.net/, which provides some recommendations.
There are two separate questions:
Are there any resources you use to check which libraries meet your
needs?
I just use the library's official documentation, or quickdocs as mentioned earlier. I don't think there are any comparison tables between similar libraries. But you can always ask for help on #lisp on Freenode IRC network (since StackOverflow doesn't like questions like "What's the best CL library for parsing CSV?")
How do you determine if a library is still being supported? Are there any heuristics short of visiting individual libraries's websites?
If a library is on Quicklisp then it is supported. Unsupported libraries usually drop out soon enough. Xach (Quicklisp's developer and maintainer) makes sure that there is no library in Quicklisp which can't be built on a supported CL implementation.
you can try http://quickdocs.org/
it contains a number of references to widely used libraries from quicklisp, shows their last update time and some documentation. As for me, it was nice starting point to avoid the choice paralysis

Recommended Scala io library [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed last year.
Improve this question
By all accounts, Scala's Source is a bit of a mess - everything I've read about it mentions resources left open, mysterious bugs...
I was wondering whether that was still the case in recent versions of Scala and, if so, what are worthy alternatives?
I've mostly heard of scala-io and scalaz-streams (and, obviously standard Java IO primitives). Did I miss anything? If anyone has experience with these or other projects, what are their respective pros and cons?
I'm inclined to go for scala-io, since I found the author's blog to be a fairly high quality source of useful of information, but I'd love to know more about the alternatives and what other people use.
Rapture IO might be worth trying.
It provides some nice DSL for managing IO resources of various kinds.
Using the package java.nio.file in Java standard library may also be simple enough if you don't require advance features. For example, to read the lines of a file into memory:
Files.readAllLines(Paths.get("file_name"), StandardCharsets.UTF_8).asScala
And to write a sequence of lines into a file:
val strs = Seq("line1", "line2", "line3")
Files.write(Paths.get("output_file"), strs.mkString("\n").getBytes())
Check
http://docs.oracle.com/javase/tutorial/essential/io/file.html
for more information.

Document Generator for library iphone [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
I have created one library, and now I want to have its documentation, so Is there any document generator available? If yes, What I have to keep in mind while generating documents.
http://www.doxygen.nl/
Doxygen is probably the most widely used option. Because it's not just for ObjC (doxygen supports many other languages), the development is lively and the community quite strong. HeaderDoc (now an open source project), by comparison appears to have largely stagnated. HeaderDoc only produces HTML output, while doxygen also produces PDF, LaTeX and many other output forms besides HTML. Even seems to recommend doxygen, with this guide to automatically producing documentation sets, compatible with 's help viewer, from within your build process.
It's worth noting that doxygen can read HeaderDoc-style comments, so you can write your documentation in HeaderDoc style and decide later whether to produce the final output using doxygen or HeaderDoc.

Where can I find some open source implementations of the Boids algorithm, for the iOs? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
The question says it all: I'm looking for working, open source, implementations of algorithms (or derivatives there of) initially described in the Boids paper.
It looks like most of the code out there was written before "Open Source" really meant anything. I asked Mr Google:
Craig Reynolds's Boids page has a bunch of links for various languages and some mostly-original Lisp. Embedding a Lisp interpreter should not be that hard.
Christopher Kline, C++, Not-For-Profit. Licence terms for commercial apps negotiable with the author.
Tom Bak, Thong Chau, Visual C++/OpenGL/GLUT, no licence. You could try contacting them.
Robert Platt, VC++/D3D, no licence. You could try contacting him too.
You're unlikely to find anything specifically "for the iOS" (or even written in Objective-C), but C and C++ versions should be easy to port. .NET versions should be easy enough to run using MonoTouch.
This might help: Chapter from Killer game programming in Java about Flocking Boids

Examples of how to visualize a versioning system? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
My shop is trying to formalize the release management process for an OSS product we maintain (edit: using SVN for version control). It's a sort of a web development framework/CMS kind of thing, as in it's a product that other projects are built on top of. This makes clear communication about the versioning system especially critical for developers that are using the tool.
I'm hoping to find some examples of how best to graph this system so we can communicate it better internally and with outside developers. I know there are lots of standards and best practices around versioning, so I'm hoping this extends to some sort of visual vocabulary as well. As one example, there is a nifty graph at http://en.wikipedia.org/wiki/Versioning#Software_Versioning_schemes. Are there any guides out there on how these sorts of things should be designed?
First, if it is an OSS project, chances are the versioning system ism a Distributed one (DVCS)
If so, then this branching model can be of interest.
The idea is to control what you want to integrate from remote repos.
alt text http://nvie.com/wp-content/uploads/2009/12/Screen-shot-2009-12-24-at-11.32.03.png
I need this too. The built-in graph in Tortoise SVN is too busy, but I've made use of it. But for soemthing like VonC's picture above, I think I'm going to go with a dry erase board and colored markers. I'll hang it outside my cube. Annotate it with revs, dates, sprints and projects, and we'll be all set.