c++: Fix up ubsan false positives on references [PR95693]
authorJakub Jelinek <jakub@redhat.com>
Fri, 22 Jan 2021 18:03:23 +0000 (19:03 +0100)
committerJakub Jelinek <jakub@redhat.com>
Fri, 22 Jan 2021 18:04:55 +0000 (19:04 +0100)
commita9ed18295bfc6d69d40af197e059e16622cd94c6
tree53b7bf20b4ae710c6154de2330c0d2a76a65d612
parent25fc4d01a8ed1888e6a65597a3387349eb3c950c
c++: Fix up ubsan false positives on references [PR95693]

Alex' 2 years old change to build_zero_init_1 to return NULL pointer with
reference type for references breaks the sanitizers, the assignment of NULL
to a reference typed member is then instrumented before it is overwritten
with a non-NULL address later on.
That change has been done to fix error recovery ICE during
process_init_constructor_record, where we:
          if (TYPE_REF_P (fldtype))
            {
              if (complain & tf_error)
                error ("member %qD is uninitialized reference", field);
              else
                return PICFLAG_ERRONEOUS;
            }
a few lines earlier, but then continue and ICE when build_zero_init returns
NULL.

The following patch reverts the build_zero_init_1 change and instead creates
the NULL with reference type constants during the error recovery.

The pr84593.C testcase Alex' change was fixing still works as before.

2021-01-22  Jakub Jelinek  <jakub@redhat.com>

PR sanitizer/95693
* init.c (build_zero_init_1): Revert the 2018-03-06 change to
return build_zero_cst for reference types.
* typeck2.c (process_init_constructor_record): Instead call
build_zero_cst here during error recovery instead of build_zero_init.

* g++.dg/ubsan/pr95693.C: New test.
gcc/cp/init.c
gcc/cp/typeck2.c
gcc/testsuite/g++.dg/ubsan/pr95693.C [new file with mode: 0644]