public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifixinc.com>
To: Duraid Madina <duraid@octopus.com.au>
Cc: gcc@gcc.gnu.org
Subject: Re: user-guided speculative precomputation? (my wacky ia64 idea)
Date: Tue, 06 Apr 2004 06:02:00 -0000	[thread overview]
Message-ID: <407247E5.5050701@specifixinc.com> (raw)
In-Reply-To: <406B5D18.7080605@octopus.com.au>

Duraid Madina wrote:
> tricky to do this automatically, but my question to the group is: would 
> it be sensible to add support for something like a "#pragma 
> delinquent_load" that could be inserted at the appropriate point in e.g. 
> graph/tree/list traversal code etc.? A "cookie cutter" prefetching 
> sequence could then be fitted in the reserved area alongside the main 
> thread

You didn't define what #pragma delinquent_load does, and I don't have a 
copy of that paper.

Probably you would have to try to implement it before you can tell 
whether you can make it work.

The limited number of bundle formats makes it difficult to reserve an 
issue slot.  You will get differing types of left-over slots depending 
on what instructions from the main thread get scheduled, and you will 
have differing types of insns that need to fit into those slots.  This 
could lead to a difficult packing problem.  And there is also the issue 
of stop bits.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

  reply	other threads:[~2004-04-06  6:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01  0:07 Duraid Madina
2004-04-06  6:02 ` Jim Wilson [this message]
2004-04-07  0:08   ` Duraid Madina
2004-04-07  1:54     ` James Morrison
2004-04-07  4:45       ` Daniel Jacobowitz
2004-04-07  5:19         ` James Morrison
2004-04-07  5:53         ` Duraid Madina
2004-04-07 23:46     ` Jim Wilson
2004-04-08  0:10       ` Duraid Madina
2004-04-08  0:39         ` Jim Wilson

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=407247E5.5050701@specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=duraid@octopus.com.au \
    --cc=gcc@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).