https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121943
--- Comment #4 from Trevor Gross <tmgross at umich dot edu> --- (In reply to Andrew Pinski from comment #2) > >However, why is this doing string comparison in the first place? It seems > >like checking the exit code would be more robust. > > Because we want to check there is no warning too. no_compiler_messages is > specifically for no warnings or otherwise. Couldn't this be covered with `-Werror`? (In reply to Andrew Pinski from comment #3) > Are you sure this is not an expect bug or a dejgnu one? I haven't traced back any further, but the garbage could indeed be coming from at any step. For reference: ``` $ dejagnu -V dejagnu auxiliary launcher (DejaGnu) 1.6.3 $ expect -v expect version 5.45.4 ```
