[Bug sanitizer/99106] New: ICE in tree_to_poly_int64, at tree.c:3091

marxin at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Mon Feb 15 14:23:03 GMT 2021


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

            Bug ID: 99106
           Summary: ICE in tree_to_poly_int64, at tree.c:3091
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

Started with the same revision as PR99033:

$ g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C -c
-fsanitize=undefined
during GIMPLE pass: ubsan
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C: In function
‘void foo()’:
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C:18:1:
internal compiler error: in tree_to_poly_int64, at tree.c:3091
   18 | }
      | ^
0x87f81e tree_to_poly_int64(tree_node const*)
        /home/marxin/Programming/gcc/gcc/tree.c:3091
0x87f81e tree_to_poly_int64(tree_node const*)
        /home/marxin/Programming/gcc/gcc/tree.c:3089
0x148775e component_ref_size(tree_node*, special_array_member*)
        /home/marxin/Programming/gcc/gcc/tree.c:13920
0x1232ece decl_init_size(tree_node*, bool)
        /home/marxin/Programming/gcc/gcc/tree-object-size.c:196
0x12336ca addr_object_size
        /home/marxin/Programming/gcc/gcc/tree-object-size.c:285
0x123556b compute_builtin_object_size(tree_node*, int, unsigned long*,
tree_node**, tree_node**)
        /home/marxin/Programming/gcc/gcc/tree-object-size.c:570
0x11a6565 instrument_object_size
        /home/marxin/Programming/gcc/gcc/ubsan.c:2150
0x11ab575 execute
        /home/marxin/Programming/gcc/gcc/ubsan.c:2405
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.


More information about the Gcc-bugs mailing list