Am 11.02.2014 16:31, schrieb Peter Maydell: > Actually this barely even rises to the level of an RFC, but > since I'm not entirely sure how or if it might be possible to > turn this into upstreamable code I thought I might as well > send it out as-is in case anybody else finds it useful. > > The basic idea is that you build the linux-user binary and > run it on something (anything). Instead of actually running > code we instead just loop round feeding every possible > instruction pattern to the decoder. This lets us catch: > * "can't happen" assertions in the wrong place > * TCG temp leaks > * insns which generate too many TCG ops > > Obvious deficiencies here: > * no UI for specifying that you want to test a smaller > part of the instruction space > * an assumption that instructions are fixed-length 32 bits > * cheesily hardwired in
Wasn't there a previous proposal to do an accel=tcgtest? That would be the way I'd expect such test frameworks to be dynamically invoked. Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
