Re: toolchain/44848: ideas for enhancing the toolchain tests

[Martin Husemann <martin%duskware.de@localhost>]

The following reply was made to PR toolchain/44848; it has been noted by GNATS.

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: mrg%eterna.com.au@localhost
Subject: Re: toolchain/44848: ideas for enhancing the toolchain tests
Date: Tue, 12 Apr 2011 11:03:22 +0200

 On Tue, Apr 12, 2011 at 06:55:03AM +0000, Jukka Ruohonen wrote:
 >  This was indeed my point; compile "hello world" (or something more involved)
 >  with various different compiler and/or linker flags on a given architecture.
 
 There are two parts to this:
 
 We should create a set of various "hello world" test binaries (where
 various includes the flags you mentioned and arch dependend also -m32
 resp. the -mabi= variations Matt mentioned).
 
 Then we should test runability of all those pre-compiled test binaries,
 exit status and output (trivial).
 
 This should be done and requires a kind of hardcoded matrix for the special
 arch dependend options (as we can't play the games the current hello32 test
 does at runtime).
 
 Another thing is to test exactly the same options matrix, but compile
 at test time, verify binaries are of proper type (i.e. by comparing
 file(1) and/or objdump output with the pregenerated test binaries from
 above), and then (of course) do the same execution tests as above for
 the freshly created binaries.
 
 Martin