From http://gcc.gnu.org/install/test.html You can run the testsuites multiple times using combinations of options with a syntax similar to the brace expansion of popular shells: ..."--target_board=arm-sim\{-mhard-float,-msoft-float\}\{-O1,-O2,-O3,\}" (Note the empty option caused by the trailing comma in the final group.) The following will run each testsuite eight times using the `arm-sim' target, as if you had specified all possible combinations yourself: --target_board=arm-sim/-mhard-float/-O1 --target_board=arm-sim/-mhard-float/-O2 --target_board=arm-sim/-mhard-float/-O3 --target_board=arm-sim/-mhard-float --target_board=arm-sim/-msoft-float/-O1 --target_board=arm-sim/-msoft-float/-O2 --target_board=arm-sim/-msoft-float/-O3 --target_board=arm-sim/-msoft-float If you run 'runtest' with multiple --target_board options only the last one will get run. The list should show: --target_board='arm-sim/-mhard-float/-O1 \ arm-sim/-mhard-float/-O2 \ arm-sim/-mhard-float/-O3 \ arm-sim/-mhard-float \ arm-sim/-msoft-float/-O1 \ arm-sim/-msoft-float/-O2 \ arm-sim/-msoft-float/-O3 \ arm-sim/-msoft-float' I.e. a single --target_board option with multiple space separated board names. That is the equivelant of the initial target_board list that uses the braces.
RUNTESTFLAGS="--target_board=unix/\{-m32,\}" works for me as well. You say the elaborated list needs fixing? Care to fix it yourself?
Yes, RUNTESTFLAGS="--target_board=unix/\{-m32,\}" works fine but RUNTESTFLAGS="--target_board=unix --target_board=unix/-m32" does not. It should be RUNTESTFLAGS="--target_board='unix unix/-m32'". I do not mind fixing it myself but I am not sure where the sources for the web pages are. Are they in the GCC source tree somewhere? I didn't see them. Should changes to the pages be sent to the gcc-patches mailing list?
(In reply to comment #2) > I am not sure where the sources > for the web pages are. Are they in the GCC source tree somewhere? > I didn't see them. Weird, IIRC instructions used to be on the write-access page. Gerald? > Should changes to the pages be sent to the > gcc-patches mailing list? yes...
(In reply to comment #3) > (In reply to comment #2) > > I am not sure where the sources > > for the web pages are. Are they in the GCC source tree somewhere? > > I didn't see them. > > Weird, IIRC instructions used to be on the write-access page. > Gerald? They are on the cvs.html page: http://gcc.gnu.org/cvs.html I don't know if they are linked from anywhere though.
OK, I can check out wwwdocs but the page I am interested in doesn't seem to be there. On the web it is http://gcc.gnu.org/install/test.html, but I can't seem to find this page in a checked out version of wwwdocs. I did get an htdocs/install directory but it does not include any files (other than CVS and .cvsignore).
(In reply to comment #5) > OK, I can check out wwwdocs but the page I am interested in doesn't seem to be > there. On the web it is http://gcc.gnu.org/install/test.html, but I can't seem > to find this page in a checked out version of wwwdocs. I did get an > htdocs/install directory but it does not include any files (other than CVS and > .cvsignore). That is generated from gcc/docs/install.texi in svn.
Author: sje Date: Wed Sep 26 22:47:22 2012 New Revision: 191781 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=191781 Log: 2012-09-26 Steve Ellcey <sellcey@mips.com> PR web/54711 * doc/install.texi: Fix example. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/install.texi
This has been resolved now with the patch to install.texi.
I addressed comments 3-6 concerning our web pages / documentation via the following two changes http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01470.html http://gcc.gnu.org/ml/gcc-patches/2012-12/msg01468.html and will be adding more over the next two weeks.