[Bug objc/53943] Compiler ICE with -fobjc-direct-dispatch flag on Linux

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53943

Eric Gallager <egallager at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
   Last reconfirmed|2017-07-27 00:00:00         |2017-10-27

--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Konstantin Osipov from comment #2)
> > kostja@atlas ~ % gcc -fobjc-direct-dispatch foo.m -lobjc
> 
> You still left off the -fobjc-exceptions flag

Update: I now have access to Linux on the GCC compile farm, and can confirm
that the ICE still happens even when adding -fobjc-exceptions:

[egallager@gcc1-power7 build]$ ${HOME}/.local/bin/gcc -fobjc-direct-dispatch
-fobjc-exceptions 53943.m -lobjc
53943.m: In function ‘main’:
53943.m:14:2: internal compiler error: Segmentation fault
  @throw [Interface new];
  ^
0x1078317b crash_signal
        ../../gcc/toplev.c:326
0x101bd670 build_function_call_vec(unsigned int, vec<unsigned int, va_heap,
vl_ptr>, tree_node*, vec<tree_node*, va_gc, vl_embed>*, vec<tree_node*, va_gc,
vl_embed>*)
        ../../gcc/c/c-typeck.c:3023
0x101697d3 build_objc_method_call
        ../../gcc/objc/objc-gnu-runtime-abi-01.c:706
0x101697d3 gnu_runtime_abi_01_build_objc_method_call
        ../../gcc/objc/objc-gnu-runtime-abi-01.c:741
0x10153b33 objc_finish_message_expr(tree_node*, tree_node*, tree_node*,
tree_node**)
        ../../gcc/objc/objc-act.c:5663
0x1015490f objc_build_message_expr(tree_node*, tree_node*)
        ../../gcc/objc/objc-act.c:5293
0x101f6e87 c_parser_postfix_expression
        ../../gcc/c/c-parser.c:8530
0x101df6eb c_parser_unary_expression
        ../../gcc/c/c-parser.c:7369
0x101e0623 c_parser_cast_expression
        ../../gcc/c/c-parser.c:7201
0x101e08db c_parser_binary_expression
        ../../gcc/c/c-parser.c:7007
0x101e15fb c_parser_conditional_expression
        ../../gcc/c/c-parser.c:6745
0x101e1c17 c_parser_expr_no_commas
        ../../gcc/c/c-parser.c:6662
0x101e1f97 c_parser_expression
        ../../gcc/c/c-parser.c:8880
0x101f26f3 c_parser_statement_after_labels
        ../../gcc/c/c-parser.c:5570
0x101f3673 c_parser_compound_statement_nostart
        ../../gcc/c/c-parser.c:5150
0x101f3dd7 c_parser_compound_statement
        ../../gcc/c/c-parser.c:4983
0x101d6487 c_parser_declaration_or_fndef
        ../../gcc/c/c-parser.c:2314
0x101fe2ab c_parser_external_declaration
        ../../gcc/c/c-parser.c:1653
0x101fed6f c_parser_translation_unit
        ../../gcc/c/c-parser.c:1534
0x101fed6f c_parse_file()
        ../../gcc/c/c-parser.c:18441
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
[egallager@gcc1-power7 build]$ 

So, confirmed.