public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: fortran/5651: Optimization (-funroll-loops) error with LAPACK sstebz.f
Date: Sun, 14 Apr 2002 05:16:00 -0000	[thread overview]
Message-ID: <20020414121602.5076.qmail@sources.redhat.com> (raw)

The following reply was made to PR fortran/5651; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "gcc-bugs@gcc.gnu.org" <gcc-gnats@gcc.gnu.org,>,
	<gcc-gnats@gcc.gnu.org>
Cc: <rth@redhat.com>
Subject: Re: fortran/5651: Optimization (-funroll-loops) error with LAPACK sstebz.f
Date: Sun, 14 Apr 2002 22:07:23 +1000

 I have done a search through CVS.  The test case:
  - passes on 2002-01-27 04:30 UTC
  - fails at 05:15 UTC
 
 The only change is:
 
  2002-01-26  Richard Henderson  <rth@redhat.com>
 
         * sched-deps.c (reg_pending_uses_head): New.
         (reg_pending_barrier): Rename from reg_pending_sets_all.
         (find_insn_list): Don't mark inline.
         (find_insn_mem_list): Remove.
         (add_dependence_list, add_dependence_list_and_free): New.
         (flush_pending_lists): Replace only_write param with separate
         for_read and for_write parameters.  Update all callers.  Use
         add_dependence_list_and_free.
         (sched_analyze_1): Do not add reg dependencies here; just set
         the pending bits.  Use add_dependence_list.
         (sched_analyze_2): Likewise.
         (sched_analyze_insn): Replace schedule_barrier_found with
         reg_pending_barrier.  Add all dependencies for pending reg
         uses, sets, and clobbers.
         (sched_analyze): Don't add reg dependencies for calls, just
         set pending bits.  Use regs_invalidated_by_call.  Treat
         sched_before_next_call as a normal list, not a fake insn.
         (init_deps): No funny init for sched_before_next_call.
         (free_deps): Free pending mems lists.  Don't zero reg_last.
         (init_deps_global): Init reg_pending_uses.
         (finish_deps_global): Free it.
         * sched-int.h (deps): Make in_post_call_group_p boolean.  Update =
 docs.
         (find_insn_mem_list): Remove.
         * sched-rgn.c (concat_INSN_LIST, concat_insn_mem_list): New.
         (propagate_deps): Use them.  Zero temp mem lists.
 
 


             reply	other threads:[~2002-04-14 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  5:16 Billinghurst, David (CRTS) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-15 20:03 rth
2002-04-15 14:45 rth
2002-04-06  2:25 billingd
2002-03-27 19:16 Craig Rodrigues
2002-03-24  2:29 toon
2002-02-10  6:36 David.Billinghurst

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=20020414121602.5076.qmail@sources.redhat.com \
    --to=david.billinghurst@riotinto.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: 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).