public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/7814: incorrect scheduling for glibc-2.2.92 stpcpy test Date: Mon, 02 Sep 2002 13:26:00 -0000 [thread overview] Message-ID: <20020902202601.8200.qmail@sources.redhat.com> (raw) The following reply was made to PR other/7814; it has been noted by GNATS. From: Glen Nakamura <glen@imodulo.com> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Cc: Subject: Re: other/7814: incorrect scheduling for glibc-2.2.92 stpcpy test Date: Mon, 2 Sep 2002 10:24:48 -1000 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7814 Okay, I think the problem is that when we flush the dependency lists (e.g. when ?_length > MAX_PENDING_LIST_LENGTH), we end up with a single insn in the 'clobbers' list while the 'sets' and 'uses' lists are empty. Now, if there is another clobber insn before any set or use insn, it won't be dependent on any previous insn because the 'sets' and 'uses' lists are empty... The problem is fixed by adding the last insn to the 'sets' list after flushing. - glen Here is the patch: ChangeLog =================================================================== 2002-09-02 Glen Nakamura <glen@imodulo.com> * sched-deps.c (sched_analyze_insn): Make sure to add insn to reg_last->sets after flushing the dependency lists to guarantee that subsequent clobbers will be dependent on it. Index: sched-deps.c =================================================================== RCS file: /cvsroot/gcc/gcc/gcc/sched-deps.c,v retrieving revision 1.34.6.1 diff -c -3 -p -u -r1.34.6.1 sched-deps.c --- sched-deps.c 19 Aug 2002 18:59:31 -0000 1.34.6.1 +++ sched-deps.c 2 Sep 2002 06:35:15 -0000 @@ -1118,8 +1118,6 @@ sched_analyze_insn (deps, x, insn, loop_ EXECUTE_IF_SET_IN_REG_SET (reg_pending_clobbers, 0, i, { struct deps_reg *reg_last = &deps->reg_last[i]; - add_dependence_list (insn, reg_last->sets, REG_DEP_OUTPUT); - add_dependence_list (insn, reg_last->uses, REG_DEP_ANTI); if (reg_last->uses_length > MAX_PENDING_LIST_LENGTH || reg_last->clobbers_length > MAX_PENDING_LIST_LENGTH) { @@ -1129,6 +1127,7 @@ sched_analyze_insn (deps, x, insn, loop_ REG_DEP_ANTI); add_dependence_list_and_free (insn, ®_last->clobbers, REG_DEP_OUTPUT); + reg_last->sets = alloc_INSN_LIST (insn, reg_last->sets); reg_last->clobbers_length = 0; reg_last->uses_length = 0; }
next reply other threads:[~2002-09-02 20:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-02 13:26 Glen Nakamura [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-02 12:46 Glen Nakamura 2002-09-02 12:26 glen
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=20020902202601.8200.qmail@sources.redhat.com \ --to=glen@imodulo.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).