On Tue, Oct 15, 2013 at 9:33 AM, Olof Kindgren <[email protected]>wrote:
> We should definitely use the great work you have done here. I have only > taken a quick glance at your test suite, so I'm not sure if it can be > easily extended with plain C or ASM test cases, but I think we want that as > well to make it easy for people to add tests without having to learn m4. > The m4 stuff generates a plain ASM file when is then assembled and linked in pretty much the most straightforward way possible, so plain ASM testcases wouldn't be difficult to add. A bit more support would be needed for C test cases, but since this is intended to be an architectural test suite, I didn't want to depend on the C compiler for the tests I've written so far, so I haven't added it yet. > What I think we should do is to use your test suite as one of the > alternative test suites (with orpsocv2, or1ksim, gcc being the other test > suites atm). The easiest way would be to put the contents of your repo in a > sub directory in openrisc/or1k-tests. If someone wants to add tests, they > can add it to your m4 infrastructure or write plain C/asm code. If we > decide to use your infrastructure as the preferred way to write tests, we > could migrate the c/asm tests one by one later on. > One way to accomplish this would be to use git submodule to integrate the various suites together into a single repo. Git subtree would be even better, but it's not installed with git by default; it's distributed in the contribs directory, so you have to manually install it. -Pete
_______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
