public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>, GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Improve jump threading dump output.
Date: Tue, 28 Sep 2021 15:53:44 +0200	[thread overview]
Message-ID: <25abc6f7-8006-5cf5-95bf-bd752a46e9ea@redhat.com> (raw)
In-Reply-To: <9f2db536-c182-426e-05d5-0242d9a109f1@gmail.com>



On 9/28/21 3:47 PM, Jeff Law wrote:
> 
> 
> On 9/28/2021 3:45 AM, Aldy Hernandez wrote:
>> In analyzing PR102511, it has become abundantly clear that we need
>> better debugging aids for the jump threader solver.  Currently
>> debugging these issues is a nightmare if you're not intimately
>> familiar with the code.  This patch attempts to improve this.
>>
>> First, I'm enabling path solver dumps with TDF_THREADING.  None of the
>> available TDF_* flags are a good match, and using TDF_DETAILS would blow
>> up the dump file, since both threaders continually call the solver to
>> try out candidates.  This will allow dumping path solver details without
>> having to resort to hacking the source.
>>
>> I am also dumping the current registered_jump_thread dbg counter used
>> by the registry, in the solver.  That way narrowing down a problematic
>> thread can then be examined by -fdump-*-threading and looking at the
>> solver details surrounding the appropriate counter (which the dbgcnt
>> also dumps to the dump file).
>>
>> You still need knowledge of the solver to debug these issues, but at
>> least now it's not entirely opaque.
>>
>> OK?
>>
>> gcc/ChangeLog:
>>
>>     * dbgcnt.c (dbg_cnt_counter): New.
>>     * dbgcnt.h (dbg_cnt_counter): New.
>>     * dumpfile.c (dump_options): Add entry for TDF_THREADING.
>>     * dumpfile.h (enum dump_flag): Add TDF_THREADING.
>>     * gimple-range-path.cc (DEBUG_SOLVER): Use TDF_THREADING.
>>     * tree-ssa-threadupdate.c (dump_jump_thread_path): Dump out
>>     debug counter.
> OK.
> 
> Note we've got massive failures in the tester starting sometime 
> yesterday and I suspect all the threader work.    So I'm going to slow 
> down on reviews of that code as we stabilize stuff.

Fair enough.  Let's knock those out then.

I just fixed a P1 that was causing undefined behavior.  Other than that, 
I don't have any known regressions apart from the loop crossing 
restrictions which you and me haven't agreed upon yet.  (Well...there 
are some archs that need testsuite tweaking, but they're not bugs per se.)

Send anything my way.

Aldy


  reply	other threads:[~2021-09-28 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28  9:45 Aldy Hernandez
2021-09-28 13:47 ` Jeff Law
2021-09-28 13:53   ` Aldy Hernandez [this message]
2021-09-28 13:56     ` Jeff Law
2021-09-28 15:45     ` Jeff Law
2021-09-28 16:05       ` Richard Biener
2021-09-28 16:13         ` Aldy Hernandez
2021-09-29  8:53           ` Richard Biener
2021-09-30  0:49             ` Jeff Law
2021-09-28 16:05       ` Richard Biener
2021-09-30 18:26     ` Jeff Law
2021-10-04 12:05       ` Aldy Hernandez
2021-10-04 13:29         ` Jeff Law

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=25abc6f7-8006-5cf5-95bf-bd752a46e9ea@redhat.com \
    --to=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    /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).