https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #11 from Eric Gallager ---
(In reply to Eric Gallager from comment #10)
> (In reply to Richard Biener from comment #2)
> > Thus,
> >
> > make check RUNTESTFLAGS="execute.exp"
> > make check RUNTESTFLAGS="dg-torture.exp"
>
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #10 from Eric Gallager ---
(In reply to Richard Biener from comment #2)
> Thus,
>
> make check RUNTESTFLAGS="execute.exp"
> make check RUNTESTFLAGS="dg-torture.exp"
Just confirming that the proper way to combine these would be:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #9 from Eric Gallager ---
(In reply to Sam James from comment #8)
> Using make synchronisation can help a bit:
> https://www.gnu.org/software/make/manual/html_node/Parallel-Output.html.
> It's made our build logs in Gentoo a lot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #8 from Sam James ---
Using make synchronisation can help a bit:
https://www.gnu.org/software/make/manual/html_node/Parallel-Output.html. It's
made our build logs in Gentoo a lot more readable for GCC, FWIW.
As for the bug request:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #7 from Jonathan Wakely ---
(In reply to Eric Gallager from comment #5)
> So, now I'm running the testsuite anyways for other reasons, and one more
> thing to note is that using any sort of parallelism when running the
> testsuite
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #6 from Eric Gallager ---
(In reply to Eric Gallager from comment #5)
> (In reply to Eric Gallager from comment #3)
> > https://gcc.gnu.org/install/test.html says "To get a list of the possible
> > *.exp files, pipe the output of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #5 from Eric Gallager ---
(In reply to Eric Gallager from comment #3)
> https://gcc.gnu.org/install/test.html says "To get a list of the possible
> *.exp files, pipe the output of ‘make check’ into a file and look at the
> ‘Running
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #4 from Eric Gallager ---
Another thing that would be useful would be to have (more) comments in the
source code saying stuff like "/* this codepath is tested by
*/" or something... although I guess it could be a problem keeping
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #3 from Eric Gallager ---
https://gcc.gnu.org/install/test.html says "To get a list of the possible *.exp
files, pipe the output of ‘make check’ into a file and look at the ‘Running …
.exp’ lines." ...has anyone stored their output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
--- Comment #2 from Richard Biener ---
I'm usually running pieces that affect the area I am patching like vect.exp for
vectorizer stuff. Generally a smoke test would be dg-torture.exp (runs C and
C++ pieces) and execute.exp (C, ObjC, Go and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103324
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2021-11-18
Ever confirmed|0
11 matches
Mail list logo
