* Setting test suite not to try debug output cases
@ 2022-09-02 18:55 Koning, Paul
2022-09-05 9:29 ` Richard Biener
0 siblings, 1 reply; 5+ messages in thread
From: Koning, Paul @ 2022-09-02 18:55 UTC (permalink / raw)
To: GCC Development
Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
xgcc: warning: target system does not support debug output
cc1: warning: target system does not support debug output
FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
paul
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Setting test suite not to try debug output cases
2022-09-02 18:55 Setting test suite not to try debug output cases Koning, Paul
@ 2022-09-05 9:29 ` Richard Biener
2022-09-05 12:23 ` Koning, Paul
0 siblings, 1 reply; 5+ messages in thread
From: Richard Biener @ 2022-09-05 9:29 UTC (permalink / raw)
To: Koning, Paul; +Cc: GCC Development
On Fri, Sep 2, 2022 at 8:57 PM Koning, Paul via Gcc <gcc@gcc.gnu.org> wrote:
>
> Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
>
> spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
> xgcc: warning: target system does not support debug output
> cc1: warning: target system does not support debug output
> FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
>
> I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
Hmm. In testsuite/lib/prune.exp there's
# Ignore stabs obsoletion warnings
regsub -all "(^|\n)\[^\n\]*\[Ww\]arning: STABS debugging
information is obsolete and not supported anymore\[^\n\]*" $text ""
text
maybe you can (selectively for pdp11) add similar pruning of the
'target system does not support debug output' message?
I think you should be able to use
if { [istarget pdp11-*-*] } then {
regsub -all " ... " ...
}
>
> paul
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Setting test suite not to try debug output cases
2022-09-05 9:29 ` Richard Biener
@ 2022-09-05 12:23 ` Koning, Paul
2022-09-05 12:27 ` Richard Biener
2022-09-05 12:29 ` Iain Sandoe
0 siblings, 2 replies; 5+ messages in thread
From: Koning, Paul @ 2022-09-05 12:23 UTC (permalink / raw)
To: Richard Biener; +Cc: GCC Development
> On Sep 5, 2022, at 5:29 AM, Richard Biener <richard.guenther@gmail.com> wrote:
>
>
> [EXTERNAL EMAIL]
>
> On Fri, Sep 2, 2022 at 8:57 PM Koning, Paul via Gcc <gcc@gcc.gnu.org> wrote:
>>
>> Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
>>
>> spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
>> xgcc: warning: target system does not support debug output
>> cc1: warning: target system does not support debug output
>> FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
>>
>> I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
>
> Hmm. In testsuite/lib/prune.exp there's
>
> # Ignore stabs obsoletion warnings
> regsub -all "(^|\n)\[^\n\]*\[Ww\]arning: STABS debugging
> information is obsolete and not supported anymore\[^\n\]*" $text ""
> text
>
> maybe you can (selectively for pdp11) add similar pruning of the
> 'target system does not support debug output' message?
> I think you should be able to use
>
> if { [istarget pdp11-*-*] } then {
> regsub -all " ... " ...
> }
Thanks, I'll look into that. Should it be more general to cover any other targets that don't have debug output? I think pdp11 isn't the only one but I'm not sure.
paul
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Setting test suite not to try debug output cases
2022-09-05 12:23 ` Koning, Paul
@ 2022-09-05 12:27 ` Richard Biener
2022-09-05 12:29 ` Iain Sandoe
1 sibling, 0 replies; 5+ messages in thread
From: Richard Biener @ 2022-09-05 12:27 UTC (permalink / raw)
To: Koning, Paul; +Cc: GCC Development
On Mon, Sep 5, 2022 at 2:23 PM Koning, Paul <Paul.Koning@dell.com> wrote:
>
>
>
> > On Sep 5, 2022, at 5:29 AM, Richard Biener <richard.guenther@gmail.com> wrote:
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Fri, Sep 2, 2022 at 8:57 PM Koning, Paul via Gcc <gcc@gcc.gnu.org> wrote:
> >>
> >> Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
> >>
> >> spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
> >> xgcc: warning: target system does not support debug output
> >> cc1: warning: target system does not support debug output
> >> FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
> >>
> >> I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
> >
> > Hmm. In testsuite/lib/prune.exp there's
> >
> > # Ignore stabs obsoletion warnings
> > regsub -all "(^|\n)\[^\n\]*\[Ww\]arning: STABS debugging
> > information is obsolete and not supported anymore\[^\n\]*" $text ""
> > text
> >
> > maybe you can (selectively for pdp11) add similar pruning of the
> > 'target system does not support debug output' message?
> > I think you should be able to use
> >
> > if { [istarget pdp11-*-*] } then {
> > regsub -all " ... " ...
> > }
>
> Thanks, I'll look into that. Should it be more general to cover any other targets that don't have debug output? I think pdp11 isn't the only one but I'm not sure.
True - pruning generally sounds more useful.
Richard.
> paul
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Setting test suite not to try debug output cases
2022-09-05 12:23 ` Koning, Paul
2022-09-05 12:27 ` Richard Biener
@ 2022-09-05 12:29 ` Iain Sandoe
1 sibling, 0 replies; 5+ messages in thread
From: Iain Sandoe @ 2022-09-05 12:29 UTC (permalink / raw)
To: Koning, Paul; +Cc: Richard Biener, GCC Development
> On 5 Sep 2022, at 13:23, Koning, Paul via Gcc <gcc@gcc.gnu.org> wrote:
>
>
>
>> On Sep 5, 2022, at 5:29 AM, Richard Biener <richard.guenther@gmail.com> wrote:
>>
>>
>> [EXTERNAL EMAIL]
>>
>> On Fri, Sep 2, 2022 at 8:57 PM Koning, Paul via Gcc <gcc@gcc.gnu.org> wrote:
>>>
>>> Given that pdp11 no longer supports debug output, I get a lot more test failures, like this:
>>>
>>> spawn -ignore SIGHUP /Users/pkoning/Documents/svn/build/pdp/gcc/xgcc -B/Users/pkoning/Documents/svn/build/pdp/gcc/ -mlra -fdiagnostics-plain-output -Og -g -w -c -o 20000105-1.o /Users/pkoning/Documents/svn/gcc/gcc/testsuite/gcc.c-torture/compile/20000105-1.c
>>> xgcc: warning: target system does not support debug output
>>> cc1: warning: target system does not support debug output
>>> FAIL: gcc.c-torture/compile/20000105-1.c -Og -g (test for excess errors)
>>>
>>> I assume there is some way in the test suite machinery to globally skip all "debug output" cases. How would I do that?
>>
>> Hmm. In testsuite/lib/prune.exp there's
>>
>> # Ignore stabs obsoletion warnings
>> regsub -all "(^|\n)\[^\n\]*\[Ww\]arning: STABS debugging
>> information is obsolete and not supported anymore\[^\n\]*" $text ""
>> text
>>
>> maybe you can (selectively for pdp11) add similar pruning of the
>> 'target system does not support debug output' message?
>> I think you should be able to use
>>
>> if { [istarget pdp11-*-*] } then {
>> regsub -all " ... " ...
>> }
>
> Thanks, I'll look into that. Should it be more general to cover any other targets that don't have debug output? I think pdp11 isn't the only one but I'm not sure.
For the parts of the testsuite that have a specific “debug.exp” you could also make the .exp do an early return like
if { [istarget pdp11-*-*] } {
return
}
That assumes that there is no point in actually compiling the testcases for “improved coverage” in some way.
Iain
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-09-05 12:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-02 18:55 Setting test suite not to try debug output cases Koning, Paul
2022-09-05 9:29 ` Richard Biener
2022-09-05 12:23 ` Koning, Paul
2022-09-05 12:27 ` Richard Biener
2022-09-05 12:29 ` Iain Sandoe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).