http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59306

            Bug ID: 59306
           Summary: ICE with -fsanitize=null: gimple check: expected
                    gimple_call(error_mark), have gimple_assign(addr_expr)
                    in gimple_call_arg
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus 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,
                    mpolacek at gcc dot gnu.org

Created attachment 31303
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31303&action=edit
Simple C++ testcase, compile with -fsanitize=null

Now that a bunch of sanitizer bugs have been fixed on the trunk, I tried
-fsanitize=null again. However, I run into another ICE with that option:

$ g++ -fsanitize=null test14.ii

test14.ii: In member function 'void
VwEventHandler::CreateEventHandlerThread()':
test14.ii:14:1: internal compiler error: gimple check: expected
gimple_call(error_mark), have gimple_assign(addr_expr) in gimple_call_arg, at
gimple.h:2477
 }
 ^
0x9d2d8c gimple_check_failed(gimple_statement_base const*, char const*, int,
char const*, gimple_code, tree_code)
        ../../gcc/gimple.c:1132
0x563c9a gimple_call_arg
        ../../gcc/gimple.h:2477

Reply via email to