On 3/17/26 8:43 AM, Tobias Burnus wrote:
Hi Jerry,
Jerry Delisle wrote:
Sorry about that Tobias, I only try to move things along.
Thanks for taking care of this. For the commit: I think it would help if
- either state that you plan to just commit it (i.e. you reviewed the
patch of someone else or because it is trivial); you can also state
that you do so after some grace period.
- or that you are requesting a review.
If you do the second but change your mind, and move from option two to one,
please send at least an email that you have now committed it.
This will avoid some confusion.
I try to do this and simply forgot.
* * *
Is there any specific way to invoke the testsuite other that make check-fortran?
Depends where you run the command:
If you run "make check-fortran" in the main build directory, it runs (cf.
Makefile):
check-fortran: check-gcc-fortran … check-target-libgomp-fortran
Namely, the gcc/testsuite/'s Fortran testsuite and the one in libgomp as well.
If you only want to run either of those, you can either run the make target
listed above or directly:
cd $build-dir/gcc; make check-fortran (to run only gcc/testsuite)
cd $build-dir/x86_64-pc-linux-gnu/libgomp/; make check
RUNTESTFLAGS="fortran.exp"
(where the x86... has to be replaced by a different triplet as applicable).
Tobias
I move forward with testing and will keep you in the loop better.
Thanks,
Jerry
