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 target/94042] [10 Regression] Bootstrap fails on ppc-linux-gnu Date: Sun, 15 Mar 2020 12:02:43 +0000 [thread overview] Message-ID: <bug-94042-4-mEHpokDkU0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94042-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94042 --- Comment #50 from Martin Liška <marxin at gcc dot gnu.org> --- commit r10-7160-g5c7e6d4bdf879b437b43037e10453275acabf521 Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Thu Mar 12 07:12:50 2020 +0000 df: Don't abuse bb->aux (PR94148, PR94042) The df dataflow solvers use the aux field in the basic_block struct, although that is reserved for any use by passes. And not only that, it is required that you set all such fields to NULL before calling the solvers, or you quietly get wrong results. This changes the solvers to use a local array for last_change_age instead, just like it already had a local array for last_visit_age. PR rtl-optimization/94148 PR rtl-optimization/94042 * df-core.c (BB_LAST_CHANGE_AGE): Delete. (df_worklist_propagate_forward): New parameter last_change_age, use that instead of bb->aux. (df_worklist_propagate_backward): Ditto. (df_worklist_dataflow_doublequeue): Use a local array last_change_age.
next prev parent reply other threads:[~2020-03-15 12:02 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-94042-4@http.gcc.gnu.org/bugzilla/> 2020-03-09 14:26 ` vmakarov at gcc dot gnu.org 2020-03-09 14:35 ` segher at gcc dot gnu.org 2020-03-09 14:37 ` marxin at gcc dot gnu.org 2020-03-09 14:44 ` segher at gcc dot gnu.org 2020-03-09 14:47 ` segher at gcc dot gnu.org 2020-03-09 14:48 ` segher at gcc dot gnu.org 2020-03-09 14:51 ` marxin at gcc dot gnu.org 2020-03-09 17:52 ` segher at gcc dot gnu.org 2020-03-09 17:53 ` segher at gcc dot gnu.org 2020-03-09 17:54 ` segher at gcc dot gnu.org 2020-03-09 18:09 ` vmakarov at gcc dot gnu.org 2020-03-09 18:15 ` marxin at gcc dot gnu.org 2020-03-09 18:40 ` marxin at gcc dot gnu.org 2020-03-09 21:35 ` segher at gcc dot gnu.org 2020-03-10 8:51 ` marxin at gcc dot gnu.org 2020-03-10 8:57 ` jakub at gcc dot gnu.org 2020-03-10 9:00 ` marxin at gcc dot gnu.org 2020-03-10 15:13 ` segher at gcc dot gnu.org 2020-03-10 15:16 ` marxin at gcc dot gnu.org 2020-03-13 17:54 ` segher at gcc dot gnu.org 2020-03-13 17:55 ` segher at gcc dot gnu.org 2020-03-15 12:02 ` marxin at gcc dot gnu.org [this message] 2020-07-13 11:12 ` segher 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-94042-4-mEHpokDkU0@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: linkBe 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).