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 rtl-optimization/94516] [10 Regression] gnutls test ./psk-file fails since r10-7515-g2c0fa3ecf70d199af18785702e9e0548fd3ab793
Date: Fri, 08 May 2020 07:31:28 +0000 [thread overview]
Message-ID: <bug-94516-4-Uj8xVIqFgn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94516-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94516
--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:af1634f1b555004753a22d1124dbb8419ee095cb
commit r11-192-gaf1634f1b555004753a22d1124dbb8419ee095cb
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri May 8 09:30:54 2020 +0200
csa: Fix --enable-checking=yes,df bootstrap failure in csa [PR94961]
My recent combine-stack-adj.c change broke df checking bootstrap,
while most of the changes are done through validate_change/confirm_changes
which update df info, the removal of REG_EQUAL notes didn't update df info.
2020-05-08 Jakub Jelinek <jakub@redhat.com>
PR bootstrap/94961
PR rtl-optimization/94516
* rtl.h (remove_reg_equal_equiv_notes): Add a bool argument
defaulted
to false.
* rtlanal.c (remove_reg_equal_equiv_notes): Add no_rescan argument.
Call df_notes_rescan if that argument is not true and returning
true.
* combine.c (adjust_for_new_dest): Pass true as second argument to
remove_reg_equal_equiv_notes.
* postreload.c (reload_combine_recognize_pattern): Don't call
df_notes_rescan.
next prev parent reply other threads:[~2020-05-08 7:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 11:52 [Bug rtl-optimization/94516] New: " marxin at gcc dot gnu.org
2020-04-07 11:54 ` [Bug rtl-optimization/94516] " marxin at gcc dot gnu.org
2020-04-07 11:58 ` marxin at gcc dot gnu.org
2020-04-07 12:01 ` rguenth at gcc dot gnu.org
2020-04-07 12:45 ` jakub at gcc dot gnu.org
2020-04-07 12:45 ` jakub at gcc dot gnu.org
2020-04-07 13:30 ` jakub at gcc dot gnu.org
2020-04-07 14:28 ` jakub at gcc dot gnu.org
2020-04-07 14:35 ` marxin at gcc dot gnu.org
2020-04-07 14:55 ` jakub at gcc dot gnu.org
2020-04-07 15:05 ` marxin at gcc dot gnu.org
2020-04-07 15:13 ` jakub at gcc dot gnu.org
2020-04-08 10:05 ` cvs-commit at gcc dot gnu.org
2020-04-08 19:29 ` jakub at gcc dot gnu.org
2020-04-08 20:02 ` law at redhat dot com
2020-04-09 13:12 ` jakub at gcc dot gnu.org
2020-04-15 9:44 ` jakub at gcc dot gnu.org
2020-04-20 13:05 ` jakub at gcc dot gnu.org
2020-05-05 14:36 ` [Bug rtl-optimization/94516] [10/11 " cvs-commit at gcc dot gnu.org
2020-05-05 14:41 ` [Bug rtl-optimization/94516] [10 " jakub at gcc dot gnu.org
2020-05-07 11:56 ` jakub at gcc dot gnu.org
2020-05-08 7:31 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2022-06-28 10:40 ` jakub at gcc dot gnu.org
2023-07-07 8:48 ` rguenth 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-94516-4-Uj8xVIqFgn@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).