public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/98690] [10/11 Regression] unexpected "'removed_return.213' may be used uninitialized in this function" causes crash since r10-3311-gff6686d2e5f797d6
Date: Fri, 15 Jan 2021 08:40:15 +0000 [thread overview]
Message-ID: <bug-98690-4-m12QXOcp6L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98690-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98690
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[10/11 Regression] |[10/11 Regression]
|unexpected |unexpected
|"'removed_return.213' may |"'removed_return.213' may
|be used uninitialized in |be used uninitialized in
|this function" causes crash |this function" causes crash
| |since
| |r10-3311-gff6686d2e5f797d6
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started when IPA SRA was added.
next prev parent reply other threads:[~2021-01-15 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 19:48 [Bug c++/98690] New: unexpected "'removed_return.213' may be used uninitialized in this function" causes crash savoiu at yahoo dot com
2021-01-15 8:29 ` [Bug ipa/98690] [10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-15 8:40 ` marxin at gcc dot gnu.org [this message]
2021-01-18 19:27 ` [Bug ipa/98690] [10/11 Regression] unexpected "'removed_return.213' may be used uninitialized in this function" causes crash since r10-3311-gff6686d2e5f797d6 jamborm at gcc dot gnu.org
2021-01-19 10:34 ` cvs-commit at gcc dot gnu.org
2021-01-19 14:54 ` cvs-commit at gcc dot gnu.org
2021-01-21 11:58 ` jakub 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-98690-4-m12QXOcp6L@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).