On Oct 2, 2006, at 6:47 PM, Jack Howarth wrote:
However in the first form with {-m32,-m64} only the -m32 tests get run with -fgnu-runtime and the -m64 tests don't (and thus fail because they can't link).

Sounds like a bug, please file a report.
I think this is a bug in objc.exp. I think the initialization code and caching code isn't multiboard safe.

I see:

mrs $ make RUNTESTFLAGS=dg.exp=defs.m\ "--target_board=unix'{,-m64}{,- fgnu-runtime}'" check-objcmrs $ grep Exec testsuite/objc/objc.log Executing on host: /Volumes/mrs3/net/gcc-darwin/gcc/xgcc -B/Volumes/ mrs3/net/gcc-darwin/gcc/ /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/ defs.m -lobjc -lobjc -lm -o ./defs.exe (timeout = 300) Executing on host: /Volumes/mrs3/net/gcc-darwin/gcc/xgcc -B/Volumes/ mrs3/net/gcc-darwin/gcc/ /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/ defs.m -lobjc -lobjc -lm -fgnu-runtime -o ./defs.exe (timeout = 300) Executing on host: /Volumes/mrs3/net/gcc-darwin/gcc/xgcc -B/Volumes/ mrs3/net/gcc-darwin/gcc/ /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/ defs.m -lobjc -lobjc -lm -m64 -o ./defs.exe (timeout = 300) Executing on host: /Volumes/mrs3/net/gcc-darwin/gcc/xgcc -B/Volumes/ mrs3/net/gcc-darwin/gcc/ /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/ defs.m -lobjc -lobjc -lm -m64 -fgnu-runtime -o ./defs.exe (timeout = 300) Executing on host: /Volumes/mrs3/net/gcc-darwin/gcc/xgcc -v (timeout = 300)

which seems right to me? Be sure to include enough context to know what it is that you're seeing that is wrong.

Anyway, I see:

Native configuration is powerpc-apple-darwin9.0.0d1

                === objc tests ===

Schedule of variations:
    unix
    unix/-fgnu-runtime
    unix/-m64
    unix/-m64/-fgnu-runtime

Running target unix
Using /Volumes/mrs3/Packages/dejagnu/baseboards/unix.exp as board description file for target. Using /Volumes/mrs3/Packages/dejagnu/config/unix.exp as generic interface file for target. Using /Volumes/mrs3/net/gcc/gcc/testsuite/config/default.exp as tool- and-target-specific interface file.
Running /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/dg.exp ...

                === objc Summary for unix ===

# of expected passes            2
Running target unix/-fgnu-runtime
Using /Volumes/mrs3/Packages/dejagnu/baseboards/unix.exp as board description file for target. Using /Volumes/mrs3/Packages/dejagnu/config/unix.exp as generic interface file for target. Using /Volumes/mrs3/net/gcc/gcc/testsuite/config/default.exp as tool- and-target-specific interface file.
Running /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/dg.exp ...

                === objc Summary for unix/-fgnu-runtime ===

# of expected passes            2
Running target unix/-m64
Using /Volumes/mrs3/Packages/dejagnu/baseboards/unix.exp as board description file for target. Using /Volumes/mrs3/Packages/dejagnu/config/unix.exp as generic interface file for target. Using /Volumes/mrs3/net/gcc/gcc/testsuite/config/default.exp as tool- and-target-specific interface file.
Running /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/dg.exp ...

                === objc Summary for unix/-m64 ===

# of expected passes            2
Running target unix/-m64/-fgnu-runtime
Using /Volumes/mrs3/Packages/dejagnu/baseboards/unix.exp as board description file for target. Using /Volumes/mrs3/Packages/dejagnu/config/unix.exp as generic interface file for target. Using /Volumes/mrs3/net/gcc/gcc/testsuite/config/default.exp as tool- and-target-specific interface file.
Running /Volumes/mrs3/net/gcc/gcc/testsuite/objc.dg/dg.exp ...

                === objc Summary for unix/-m64/-fgnu-runtime ===

# of expected passes            2

                === objc Summary ===

# of expected passes            8
/Volumes/mrs3/net/gcc-darwin/gcc/xgcc version 4.2.0 20060929 (experimental)

so things are now working just fine for me.

Reply via email to