On Mon, 2008-12-01 at 08:59 -0500, Jack Howarth wrote: > Doug, > Is there a reason why prune.exp is loaded in lib/gcc.exp and lib/g++.exp > but never actually used? I need to prune a linker warning with.. > > regsub -all "(^|\n)ld: warning: can't make compact unwind encoding from dwarf > for \[^\n\]* in \[^\n\]*" $text "" text > > on x86_64-apple-darwin10 to suppress false failures in dg-struct-layout-1 > for gcc.dg and g++.dg. Elsewhere in the testsuite, I can suppress these > warnings easily by placing that line in lib/prune.exp. However it is > unclear how I should code this pruning into lib/g++.exp and lib/gcc.exp > so that the dg-struct-layout-1 false excessive error failures are > suppressed. Any advice would be appreciated.
Jack, The compat tests use different procedures to compile and link, defined in lib/compat.exp. Those could call prune_gcc_output, or compat tests could be made to handle dg-prune-output directives in tests by modifying compat-get-options-main in compat.exp. Janis
