[M3devel] gcc tree checking

[Olaf Wagner]

Quoting "Rodney M. Bates" <rodney_bates at lcwb.coop>:

> Jay K wrote:
[...]
>> I'm thinking maybe I should make a test case that thoroughly exercise
>> each m3cg opcode and verifies that the output assembly is unchanged,
>> for a few architectures.
>
> This is a very good idea.  It may be a lot of work, but I have found
> many times over that regression testing tools of this kind pay for
> themselves in the (not so) long run.  Some of the changes found will
> be legitimate, but that's a lot easier to verify than to chase obscure
> bugs from end symptoms.

I second that. Regression testing for the generated code would be
great and give us much more safefy when changing the compiler.

So anybody who'd like to work in this area is greatly encouraged.

Of course a general easily extensible framework would be nice :-)
Preferrably written in quake and M3.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194