public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ghassan Shobaki <gshobaki@ece.ucdavis.edu>
To: Jan Hubicka <jh@suse.cz>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
	gcc-help@gcc.gnu.org, Jan Hubicka <hubicka@ucw.cz>
Subject: Re: Trace Scheduling in GCC
Date: Tue, 15 Feb 2005 09:18:00 -0000	[thread overview]
Message-ID: <Pine.GHP.4.58.0502141224450.12092@dante.ece.ucdavis.edu> (raw)
In-Reply-To: <20050214174039.GU18978@kam.mff.cuni.cz>

Honza,

But what will happen if I try to bypass the tail duplication stage? In
theory that should generate traces. However, the question is will the
data dependence graph construction and scheduling stages still work? (for
my purposes, the scheduler does not have to produce correct schedules,
since all what I need is importing the data dependence graphs to
feed them into my standalone scheduler. So, it is all about the data
dependence graphs for my purpose).

Thanks
-Ghassan


On Mon, 14 Feb 2005, Jan Hubicka wrote:

> > >
> > >I am right about the functionalities of these options?
> > >It seems to me that none of these options meets my objective of studying
> > >traces that have mltiple entrances and multiple exits. Please correct me
> > >if I am wrong. And if I am right, is there another way for me to get what
> > >I want, may be by doing some quick hack that bypasses tail duplication
> > >under the -fsched2-use-tarces option -does this make sense?
> > >
> > >
> > >
> > Sorry, I don't know this code well.  I am in the same position as you.
> > I should research the code to answer your questions.  I think Jan is
> > the right person to do it.  Because he wrote this code.
>
> The -fsched2-use-traces is simple superblock scheduler that is preceeded
> by trace discovery and tail duplication pass.
> So if you want traces directly, you might steal the code from tracer.c
> but except for that I don't think it suits your needs very well,
> unforutnately.
>
> Honza
> >
> > Vlad
> >
>

  reply	other threads:[~2005-02-14 20:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03  6:14 Superblock Instruction " Ghassan Shobaki
2003-12-03 14:03 ` Vladimir N. Makarov
2003-12-04  0:06   ` Jan Hubicka
2003-12-04  1:26     ` Ghassan Shobaki
2003-12-04 10:25       ` Jan Hubicka
2003-12-04 15:54         ` Vladimir Makarov
2003-12-09 21:11     ` Ghassan Shobaki
2004-01-28  1:31     ` Superblock Instruction Scheduling in GCC 3.4 Ghassan Shobaki
2004-01-28 12:23       ` Jan Hubicka
2004-01-29  7:07         ` Ghassan Shobaki
2004-01-29 10:13           ` Jan Hubicka
2004-02-01 18:17             ` Ghassan Shobaki
2004-02-01 21:55               ` Jan Hubicka
2004-02-02  5:52                 ` Ghassan Shobaki
2004-02-10 18:57                 ` Superblock Scheduling Alg in GCC Ghassan Shobaki
2004-02-10 20:08                   ` Vladimir Makarov
2004-02-10 20:17                     ` Vladimir Makarov
2004-02-10 20:27                       ` Jan Hubicka
2004-04-14 17:03                         ` Ghassan Shobaki
2004-04-14 22:44                           ` Vladimir Makarov
     [not found]                             ` <Pine.LNX.4.58.0404142056120.4634@hawking.ece.ucdavis.edu>
2004-04-17 19:29                               ` Ghassan Shobaki
2004-05-27  6:41                         ` Ghassan Shobaki
2004-05-27 10:06                           ` Tree-SSA: Grammer Sumit Jain
2004-05-27 12:56                             ` llewelly
2005-02-11 16:55                           ` Trace Scheduling in GCC Ghassan Shobaki
     [not found]                             ` <4210D6C0.3030005@redhat.com>
2005-02-15  6:30                               ` Vladimir Makarov
2006-11-24 18:42                                 ` Phase Ordering of Scheduling and Allocation " Ghassan Shobaki
2006-11-24 19:28                                   ` Vladimir N. Makarov
2005-02-15  7:45                               ` Trace Scheduling " Jan Hubicka
2005-02-15  9:18                                 ` Ghassan Shobaki [this message]
2005-02-17 16:19                                   ` Jan Hubicka
2005-02-16 10:40                               ` Vladimir Makarov
     [not found]                                 ` <Pine.GHP.4.58.0502150840080.14429@dante.ece.ucdavis.edu>
2005-02-16 11:19                                   ` Jan Hubicka

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=Pine.GHP.4.58.0502141224450.12092@dante.ece.ucdavis.edu \
    --to=gshobaki@ece.ucdavis.edu \
    --cc=gcc-help@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jh@suse.cz \
    --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).