public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/54878] libgfortran issues found by the Coverity scanner
Date: Thu, 16 Dec 2021 18:23:45 +0000 [thread overview]
Message-ID: <bug-54878-4-lZ2Dy0Y0Bp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54878-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54878
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu.org
--- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
The followings don't exist anymore in the current code: a, b, c, h.
d) is still present, but it is for generated code, due to the very generic way
the code is being generated. Not an issue.
e) is still present. I think it's guaranteed that base is not NULL, but someone
might want to double-check the logic there.
f) was fixed in:
commit a0b012be6aef65bd11107f8dac814c3ac36f95d0
Author: Tobias Burnus <burnus@net-b.de>
Date: 2013-03-29 10:32:57 +0100
g) Not sure why it's considered bad practice to ignore the return value of a
function call. In some cases, it's not a problem.
prev parent reply other threads:[~2021-12-16 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 20:55 [Bug fortran/54878] New: " burnus at gcc dot gnu.org
2012-10-10 18:42 ` [Bug fortran/54878] " burnus at gcc dot gnu.org
2014-12-21 12:37 ` dominiq at lps dot ens.fr
2021-12-16 18:23 ` fxcoudert at gcc dot gnu.org [this message]
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-54878-4-lZ2Dy0Y0Bp@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).