diff options
| author | Sandra Loosemore <sandra@codesourcery.com> | 2020-09-19 07:32:35 -0700 |
|---|---|---|
| committer | Sandra Loosemore <sandra@codesourcery.com> | 2020-09-19 13:54:16 -0700 |
| commit | a85e5696a31cac8c14dde14f031e76480205f8a0 (patch) | |
| tree | 641ac163c58884fdc6ac9520a06a505a5a03930b /gcc/objc | |
| parent | 83e037364e0d6dd74d595751e8bc8c461b4cb8fa (diff) | |
| download | gcc-a85e5696a31cac8c14dde14f031e76480205f8a0.zip gcc-a85e5696a31cac8c14dde14f031e76480205f8a0.tar.gz gcc-a85e5696a31cac8c14dde14f031e76480205f8a0.tar.bz2 | |
Work around bootstrap failure in Fortran front end.
Switching the C++ front end to lower loops the same was as the C front
end triggered this error when bootstrapping the Fortran front end:
/path/to/gcc/fortran/interface.c:3546:12: error: '*new_arg' may be used uninitialized [-Werror=maybe-uninitialized]
3546 | new_arg[i]->next = NULL;
| ~~~~~~~~~^
Work around this by adding an assertion, which seems appropriate for
documentation and good coding practices anyway.
2020-08-12 Sandra Loosemore <sandra@codesourcery.com>
gcc/fortran/
* interface.c (gfc_compare_actual_formal): Add assertion after
main processing loop to silence maybe-uninitialized error.
Diffstat (limited to 'gcc/objc')
0 files changed, 0 insertions, 0 deletions