Ah okay, thanks! On Oct 11, 2016 8:25 PM, "Ömer Sinan Ağacan" <[email protected]> wrote:
> > Is it not possible to unit test GHC? > > You need to export functions you want to test, and then write a program > that > tests those functions using the `ghc` package. > > See > https://github.com/ghc/ghc/blob/master/testsuite/tests/ > unboxedsums/unboxedsums_unit_tests.hs > for an example. > > 2016-10-11 17:50 GMT-04:00 Thomas Jakway <[email protected]>: > >> I read somewhere that fixing the graph register allocator would be a good >> project so I thought I'd look into it. I couldn't find any tickets about it >> on Trac though so I was poking around for tests to see what (if anything) >> was wrong with it. >> >> After I sent that last email I googled around for how to write ghc unit >> tests and this >> <https://mail.haskell.org/pipermail/ghc-devs/2014-January/003916.html> >> is the only thing I found. Is it not possible to unit test GHC? If not >> are there plans/discussions about this? I think it'd help document the >> code base if nothing else and it'd be a good way to get my feet wet. >> On 10/11/2016 02:13 PM, Ben Gamari wrote: >> >> Thomas Jakway <[email protected]> <[email protected]> writes: >> >> >> Can anyone point me to the register allocator tests (especially for the >> graph register allocator)? Can't seem to find them and grepping doesn't >> turn up much (pretty much just >> testsuite/tests/codeGen/should_run/cgrun028.h). >> >> >> What sort of tests are you looking for in particular? I'm afraid all we >> have are regression tests covering the code generator as a whole. >> >> Cheers, >> >> - Ben >> >> >> >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs >> >> >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
