public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/98408] Character lengths for allocatable character arrays
Date: Sun, 14 Feb 2021 12:16:47 +0000 [thread overview]
Message-ID: <bug-98408-4-f0lUPa8PaN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98408-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98408
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-02-14
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Compiling the test with -Wall gives
2 | character (len=:), allocatable :: a(:)
| ^
Warning: '.a' is used uninitialized [-Wuninitialized]
> Not so much a bug as a 'feature', I'm afraid.
Does it mean "another false positive for -Wuninitialized"?
next prev parent reply other threads:[~2021-02-14 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 8:35 [Bug fortran/98408] New: " tkoenig at gcc dot gnu.org
2020-12-21 10:33 ` [Bug fortran/98408] " pault at gcc dot gnu.org
2021-02-14 12:16 ` dominiq at lps dot ens.fr [this message]
2023-03-28 10:09 ` pault at gcc dot gnu.org
2023-04-08 8:04 ` cvs-commit at gcc dot gnu.org
2023-04-08 9:36 ` pault at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-98408-4-f0lUPa8PaN@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).