# Gfortran uninitialized warnings

**URL:** <https://fortran-lang.discourse.group/t/gfortran-uninitialized-warnings/3838>\
**Category:** Uncategorized\
**Created:** [June 26, 2022, 10:31am UTC](https://fortran-lang.discourse.group/t/gfortran-uninitialized-warnings/3838 "2022-06-26T10:31:50Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [June 26, 2022, 11:20am UTC](https://fortran-lang.discourse.group/t/gfortran-uninitialized-warnings/3838/4 "2022-06-26T11:20:15Z")

</div>

I did a more thorough search for bug reports in GCC and I found some existing bug reports for gfortran, namely:

- [56670 – Allocatable-length character var causes bogus warning with -Wuninitialized](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56670)
- [91442 – Wrong "may be used uninitialized" warning with allocation on assignment](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91442)
- [77504 – [10/11/12/13 Regression] "is used uninitialized" with allocatable string and array constructors](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504)

Full [Bug List](https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&component=fortran&list_id=350228&query_format=advanced&short_desc=uninitialized&short_desc_type=allwordssubstr)

---

_[View the full topic](https://fortran-lang.discourse.group/t/gfortran-uninitialized-warnings/3838)._
