[Bug testsuite/45692] FAIL: objc/execute/exceptions/throw-nil.m execution on darwin with -m32
--- Comment #2 from nicola at gcc dot gnu dot org 2010-09-17 10:14 --- Ok ... I fixed the testcase in trunk. Please can you let me know if it works fine now (I don't have a darwin machine to test). :-) Thanks -- nicola at gcc dot gnu dot org changed: What|Removed |Added Status|ASSIGNED|WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45692
[Bug testsuite/45692] FAIL: objc/execute/exceptions/throw-nil.m execution on darwin with -m32
--- Comment #3 from dominiq at lps dot ens dot fr 2010-09-17 12:42 --- Ok ... I fixed the testcase in trunk. Is there not a simpler way to fix the test with dejagnu directives? Please can you let me know if it works fine now With the new test the failures are gone. Thanks. (I don't have a darwin machine to test). :-) You can always monitor the regress bot on http://gcc.gnu.org/ml/gcc-testresults/2010-*. When nobody has broken its bootstrap, you can get an idea of what's wrong with darwin three times a day. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45692
[Bug testsuite/45692] FAIL: objc/execute/exceptions/throw-nil.m execution on darwin with -m32
--- Comment #4 from nicola at gcc dot gnu dot org 2010-09-17 16:40 --- Ok ... I fixed the testcase in trunk. Is there not a simpler way to fix the test with dejagnu directives? Probably. :-) The fix in trunk does work and is consistent with other files in the same directory. But feel free to suggest a better way, and send a patch. We could maybe tidy up all the files in that directory ;-) Thanks -- nicola at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45692
[Bug testsuite/45692] FAIL: objc/execute/exceptions/throw-nil.m execution on darwin with -m32
--- Comment #5 from iains at gcc dot gnu dot org 2010-09-17 17:05 --- (In reply to comment #4) Ok ... I fixed the testcase in trunk. Is there not a simpler way to fix the test with dejagnu directives? Probably. :-) well that's why I added the /torture dir under objc.dg - if tests require that .. (also obj-c++.gc/torture) If possible, it would be better to add all new tests under objc.dg/{,torture,} as necessary... and avoid objc/* .. it gives access to more flexible and selective features - which can help in the transition to ObjC2 on NeXT. if there are a significant number of new gnu-runtime-only-torture tests - then perhaps we should create a gnu-runtime subdir under the torture heading. If there are not many that are gnu-only (as at present) then dg-skip works for me. We could maybe tidy up all the files in that directory ;-) yeah, it would be good to move all of the objc/* to objc.dg - when someone has time. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45692