public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Towner <daniel.towner@picochip.com>
To: "Vladimir N. Makarov" <vmakarov@redhat.com>
Cc: gcc@gcc-patches.gnu.org, Steven Bosscher <stevenb@suse.de>,
	Nathan Sidwell <nathan@codesourcery.com>,
	gcc@gcc.gnu.org
Subject: Re: Incorrect DFA scheduling of output dependency.
Date: Wed, 08 Dec 2004 09:53:00 -0000	[thread overview]
Message-ID: <41B6CEE5.9080208@picochip.com> (raw)
In-Reply-To: <41B6360E.6010806@redhat.com>


>> Please try the following patch if it works for you, I could commit it 
>> into the main line.  It should solve the problem of generation of 
>> incorrect schedule for VLIW.  But the problem of generation of not 
>> optimal schedule will still exist because the first insn after the 
>> barrier behaves as one setting and using all registers.
>>                                                                                
>>
>>        * sched-deps.c (sched_analyze_insn): Use more accurate dependence
>>        type for the first insn after MOVE_BARRIER.
>>  
>
> Sorry, the previous patch had some typos and failed to be compiled.  
> So here is the correct version of the patch.


Yes, that works.

Thanks for your help everyone.

dan.

      parent reply	other threads:[~2004-12-08  9:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 11:30 Daniel Towner
2004-12-06 12:30 ` Nathan Sidwell
2004-12-06 12:31 ` Steven Bosscher
2004-12-06 16:27   ` Daniel Towner
2004-12-06 17:12     ` Vladimir Makarov
2004-12-07 10:59       ` Daniel Towner
2004-12-07 13:01         ` Steven Bosscher
2004-12-07 13:15           ` Steven Bosscher
2004-12-07 13:26             ` Jeffrey A Law
2004-12-07 13:40               ` Daniel Berlin
2004-12-07 22:15         ` Vladimir N. Makarov
     [not found]           ` <41B6360E.6010806@redhat.com>
2004-12-08  9:53             ` Daniel Towner [this message]

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=41B6CEE5.9080208@picochip.com \
    --to=daniel.towner@picochip.com \
    --cc=gcc@gcc-patches.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=nathan@codesourcery.com \
    --cc=stevenb@suse.de \
    --cc=vmakarov@redhat.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).