public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94774] Uninitialized variable retval in function try_substitute_return_value
Date: Wed, 29 Apr 2020 13:54:08 +0000	[thread overview]
Message-ID: <bug-94774-4-4B3UyCt2fD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94774-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94774

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Stefan Schulze Frielinghaus
<stefansf@gcc.gnu.org>:

https://gcc.gnu.org/g:1657178f59bf0c5b269a668bcdcc432fac3bbdd0

commit r10-8050-g1657178f59bf0c5b269a668bcdcc432fac3bbdd0
Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com>
Date:   Mon Apr 27 18:09:07 2020 +0200

    tree-optimization: Fix use of uninitialized variable [PR94774]

    Array retval is not necessarily initialized by function is_call_safe and
    may be used afterwards.  Thus, initialize it explicitly.

    gcc/ChangeLog:

    2020-04-29  Stefan Schulze Frielinghaus  <stefansf@linux.ibm.com>

            PR tree-optimization/94774
            * gimple-ssa-sprintf.c (try_substitute_return_value): Initialize
            variable retval.

  parent reply	other threads:[~2020-04-29 13:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 15:05 [Bug middle-end/94774] New: " stefansf at linux dot ibm.com
2020-04-27 15:34 ` [Bug tree-optimization/94774] " msebor at gcc dot gnu.org
2020-04-27 16:51 ` stefansf at linux dot ibm.com
2020-04-29 13:54 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-03 18:48 ` manu 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-94774-4-4B3UyCt2fD@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).