At r157738, the testsuite testcase objc.dg/objc-gc-4.m -fgnu-runtime now fails with an internal compiler error on x86_64-apple-darwin10... Executing on host: /sw/src/fink.build/gcc45-4.4.999-20100325/darwin_objdir/gcc/xgcc -B/sw/src/fink.build/gcc45-4.4.999-20100325/darwin_objdir/gcc/ /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m -fgnu-runtime -fobjc-gc -I/sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/../../libobjc -B/sw/src/fink.build/gcc45-4.4.999-20100325/darwin_objdir/x86_64-apple-darwin10.3.0/./libobjc/.libs -L/sw/src/fink.build/gcc45-4.4.999-20100325/darwin_objdir/x86_64-apple-darwin10.3.0/./libobjc/.libs -S -o objc-gc-4.s (timeout = 300) /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m: In function '-[MyRTFFileDocument readFromFile:ofType:]': /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m:58:13: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. compiler exited with status 1 output is: /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m: In function '-[MyRTFFileDocument readFromFile:ofType:]': /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m:58:13: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. FAIL: objc.dg/objc-gc-4.m -fgnu-runtime (internal compiler error) FAIL: objc.dg/objc-gc-4.m -fgnu-runtime (test for excess errors) Excess errors: /sw/src/fink.build/gcc45-4.4.999-20100325/gcc-4.5-20100325/gcc/testsuite/objc.dg/objc-gc-4.m:58:13: internal compiler error: Segmentation fault
I believe that this test was not previously carried out with "-fgnu-runtime" . So, technically I think it's a failed New test rather than a regression (but I will triple-check a little later). In any event, I don't suppose we want an ICE as a response to a command line error.
A backtrace shows... Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000 assemble_external (decl=0x0) at ../../gcc-4.5-20100325/gcc/varasm.c:2372 2372 if (!DECL_P (decl) || !DECL_EXTERNAL (decl) || !TREE_PUBLIC (decl)) (gdb) bt #0 assemble_external (decl=0x0) at ../../gcc-4.5-20100325/gcc/varasm.c:2372 #1 0x000000010000d99f in objc_generate_write_barrier (lhs=<value temporarily unavailable, due to optimizations>, modifycode=<value temporarily unavailable, due to optimizations>, rhs=<value temporarily unavailable, due to optimizations>) at ../../gcc-4.5-20100325/gcc/objc/objc-act.c:3152 #2 0x0000000100035cc2 in build_modify_expr (location=487750, lhs=0x1424328c0, lhs_origtype=0x1424a09d8, modifycode=NOP_EXPR, rhs_loc=1112148440, rhs=0x1424aa640, rhs_origtype=0x0) at ../../gcc-4.5-20100325/gcc/c-typeck.c:4815 #3 0x000000010006fd11 in c_parser_expr_no_commas (parser=<value temporarily unavailable, due to optimizations>, after=<value temporarily unavailable, due to optimizations>) at ../../gcc-4.5-20100325/gcc/c-parser.c:4609 #4 0x000000010006fe26 in c_parser_expression (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:6000 #5 0x00000001000701d1 in c_parser_expression_conv (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:6025 #6 0x0000000100073a1e in c_parser_statement_after_labels (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3895 #7 0x0000000100075833 in c_parser_compound_statement_nostart (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3575 #8 0x0000000100076d3d in c_parser_compound_statement (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3413 #9 0x0000000100074fac in c_parser_statement_after_labels (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3988 #10 0x0000000100074c3d in c_parser_statement_after_labels (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:4018 #11 0x0000000100075833 in c_parser_compound_statement_nostart (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3575 #12 0x0000000100076d3d in c_parser_compound_statement (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:3413 #13 0x0000000100078d14 in c_parser_external_declaration (parser=0x14154a038) at ../../gcc-4.5-20100325/gcc/c-parser.c:6446 #14 0x0000000100079a44 in c_parse_file () at ../../gcc-4.5-20100325/gcc/c-parser.c:1005 #15 0x000000010005fe55 in c_common_parse_file (set_yydebug=<value temporarily unavailable, due to optimizations>) at ../../gcc-4.5-20100325/gcc/c-opts.c:1283 #16 0x00000001005a9e08 in toplev_main (argc=25, argv=0x7fff5fbfeb78) at ../../gcc-4.5-20100325/gcc/toplev.c:1053 #17 0x0000000100001664 in start ()
Subject: Re: ICE on objc.dg/objc-gc-4.m -fgnu-runtime I think there is an already filed bug about this option with the gnu runtime also. This option should not be supported or a nop there. Sent from my iPhone On Mar 26, 2010, at 5:16 AM, "developer at sandoe-acoustics dot co dot uk" <gcc-bugzilla@gcc.gnu.org> wrote: > > > ------- Comment #1 from developer at sandoe-acoustics dot co dot uk > 2010-03-26 12:16 ------- > I believe that this test was not previously carried out with "-fgnu- > runtime" . > > So, technically I think it's a failed New test rather than a > regression (but I > will triple-check a little later). > > In any event, I don't suppose we want an ICE as a response to a > command line > error. > > > -- > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43535 >
(In reply to comment #3) > Subject: Re: ICE on objc.dg/objc-gc-4.m -fgnu-runtime > This option should not be supported or a nop there. if gc is incompatible with gnu runtime then that should be thrown out either in options processing - or in objc init.. .. I'm happy to take on doing the latter ; the question then is error or remove the flag and warn?
*** This bug has been marked as a duplicate of 35996 ***