public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tejohnson at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/63432] [5 Regression] profiledbootstrap failure with bootstrap-lto Date: Tue, 07 Oct 2014 18:58:00 -0000 [thread overview] Message-ID: <bug-63432-4-37HQNsFmWl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63432-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63432 --- Comment #21 from Teresa Johnson <tejohnson at google dot com> --- On Tue, Oct 7, 2014 at 11:08 AM, Jeff Law <law@redhat.com> wrote: > On 10/04/14 13:29, Teresa Johnson wrote: >>> >>> Jeff, what is intended here - should we not be threading both of these >>> paths? >> >> >> I have a patch to make the mark_threaded_blocks checking of paths work >> regardless of the ordering of paths in the vec. This fixes the >> failure. > > This seems like a better solution. It'll decrease unnecessary block > copying. Ok, great. The patch I posted had a bug I introduced when cleaning it up that was caught by my LTO profiledbootstrap in that I wasn't resetting the e->aux pointer back to NULL when canceling the jump thread. I am kicking off the testing again and should hopefully have a final patch to send to gcc-patches later today. > >> >> The other approach is whenever we finish threading a path, go through >> the vec of remaining paths and update the edges for any that have been >> affected by the threading and that should instead include the >> duplicated edges. > > That'd probably work too, but I suspect there's not much, if any, benefit to > keeping both paths. Yeah, in this case the extra threading worked from a correctness standpoint but doesn't make sense from a logical or performance standpoint. > I typically have to draw out the CFG and the intermediate steps to gain clarity into the desired result and there's not enough info here to do that. I'm glad I'm not the only one who has to draw it out every time! Thanks, Teresa > > Jeff
next prev parent reply other threads:[~2014-10-07 18:58 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63432-4@http.gcc.gnu.org/bugzilla/> 2014-10-01 16:25 ` tejohnson at google dot com 2014-10-03 15:59 ` hjl.tools at gmail dot com 2014-10-03 16:14 ` tejohnson at google dot com 2014-10-03 17:27 ` tejohnson at google dot com 2014-10-03 18:28 ` tejohnson at google dot com 2014-10-03 19:48 ` hjl.tools at gmail dot com 2014-10-03 19:58 ` hjl.tools at gmail dot com 2014-10-03 20:18 ` tejohnson at google dot com 2014-10-03 20:23 ` hjl.tools at gmail dot com 2014-10-03 22:35 ` tejohnson at google dot com 2014-10-04 6:16 ` tejohnson at google dot com 2014-10-04 15:34 ` tejohnson at google dot com 2014-10-04 19:30 ` tejohnson at google dot com 2014-10-07 15:54 ` tejohnson at google dot com 2014-10-07 18:09 ` law at redhat dot com 2014-10-07 18:58 ` tejohnson at google dot com [this message] 2014-10-09 4:39 ` tejohnson at gcc dot gnu.org 2014-10-09 20:38 ` tejohnson at google dot com 2014-10-10 2:12 ` tejohnson at google dot com 2014-10-10 15:15 ` hjl.tools at gmail dot com 2014-10-13 15:53 ` hjl.tools at gmail dot com 2014-10-13 21:33 ` tejohnson at google dot com 2014-10-14 14:42 ` tejohnson at google dot com 2014-10-15 15:46 ` tejohnson at gcc dot gnu.org 2014-11-19 13:30 ` rguenth at gcc dot gnu.org 2014-11-24 13:36 ` 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-63432-4-37HQNsFmWl@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).