From: Thomas Koenig <tkoenig@netcologne.de>
To: Jerry D <jvdelisle2@gmail.com>, Harald Anlauf <anlauf@gmx.de>,
gfortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, libgfortran] Initailize some variable to get rid of nuisance warnings.
Date: Mon, 27 Feb 2023 07:30:21 +0100 [thread overview]
Message-ID: <6f412291-692f-1a99-2b13-600350741bdd@netcologne.de> (raw)
In-Reply-To: <453af0ec-7fe6-bb7c-188d-787616494cc4@gmail.com>
Hi Jerry,
> I should have clarified in my posts that the warnings are on the use of
> sstride[0], mstride[0] or both.
> In a sense it is a
> regression. It showed up when builds started to use -Wmaybe-unitialized.
I think this is OK for trunk now, and backport for up to whenever
-Wmaybe-uninitialized was introduced into the build.
The "regression-only" rule is mostly motivated by not introducing
new bugs (and for Fortran, we have a bit of leeway), and I would
be hard to pressed to think of a patch less likely to introduce
regressions.
Thanks for the patch!
Best regards
Thomas
next prev parent reply other threads:[~2023-02-27 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 19:52 Jerry D
2023-02-26 20:59 ` Harald Anlauf
2023-02-26 20:59 ` Harald Anlauf
2023-02-27 2:53 ` Jerry D
2023-02-27 6:30 ` Thomas Koenig [this message]
2023-02-27 7:54 ` Tobias Burnus
2023-02-28 2:16 ` Jerry D
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=6f412291-692f-1a99-2b13-600350741bdd@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
/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).