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 ipa/97404] [9/10 Regression] aarch64: Wrong code since r9-3666-g74ca1c01d
Date: Fri, 16 Oct 2020 08:52:44 +0000 [thread overview]
Message-ID: <bug-97404-4-RjgcY5gdRI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97404-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97404
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:3faef34e9e0888ad82a115a5a7d775d299863c4f
commit r9-8999-g3faef34e9e0888ad82a115a5a7d775d299863c4f
Author: Martin Liska <mliska@suse.cz>
Date: Thu Oct 15 14:57:31 2020 +0200
IPA: compare VRP types.
gcc/ChangeLog:
PR ipa/97404
* ipa-prop.c (struct ipa_vr_ggc_hash_traits):
Compare types of VRP as we can merge ranges of different types.
gcc/testsuite/ChangeLog:
PR ipa/97404
* gcc.c-torture/execute/pr97404.c: New test.
(cherry picked from commit a86623902767122c71c7229150a8b8a79cbb3673)
next prev parent reply other threads:[~2020-10-16 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 16:36 [Bug ipa/97404] New: [9/10/11 " acoplan at gcc dot gnu.org
2020-10-13 18:19 ` [Bug ipa/97404] " marxin at gcc dot gnu.org
2020-10-14 6:20 ` rguenth at gcc dot gnu.org
2020-10-16 7:44 ` cvs-commit at gcc dot gnu.org
2020-10-16 7:53 ` marxin at gcc dot gnu.org
2020-10-16 8:52 ` [Bug ipa/97404] [9/10 " cvs-commit at gcc dot gnu.org
2020-10-16 8:52 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-16 8:53 ` marxin 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-97404-4-RjgcY5gdRI@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).