diff options
| author | Manuel López-Ibáñez <manu@gcc.gnu.org> | 2015-09-25 14:24:11 +0000 |
|---|---|---|
| committer | Manuel López-Ibáñez <manu@gcc.gnu.org> | 2015-09-25 14:24:11 +0000 |
| commit | 41d9f1e0397b3661f765d21d8397e2a54aa4cd55 (patch) | |
| tree | 21100e9b2f3e1a93346e76fdaba64fa8547b8ad1 /gcc/config.gcc | |
| parent | f700c7caef3feffdadcac957ac92f8c5d8470270 (diff) | |
| download | gcc-41d9f1e0397b3661f765d21d8397e2a54aa4cd55.zip gcc-41d9f1e0397b3661f765d21d8397e2a54aa4cd55.tar.gz gcc-41d9f1e0397b3661f765d21d8397e2a54aa4cd55.tar.bz2 | |
PR pretty-print/67567 do not pass NULL as a string
Fortran passes NULL where a non-null string is expected by the pretty-printer,
which causes a sanitizer warning. This could have been found earlier by using
gcc_checking_assert. Even if the assertion is false, the result is just an
incomplete diagnostic, thus it seems more user-friendly to assert only when
checking. I do not have any idea how to properly fix the Fortran bug, thus this
patch simply works-around it.
gcc/fortran/ChangeLog:
2015-09-25 Manuel López-Ibáñez <manu@gcc.gnu.org>
PR pretty-print/67567
* resolve.c (resolve_fl_procedure): Work-around when iface->module
== NULL.
gcc/ChangeLog:
2015-09-25 Manuel López-Ibáñez <manu@gcc.gnu.org>
PR pretty-print/67567
* pretty-print.c (pp_string): Add gcc_checking_assert.
* pretty-print.h (output_buffer_append_r): Likewise.
From-SVN: r228131
Diffstat (limited to 'gcc/config.gcc')
0 files changed, 0 insertions, 0 deletions