From: Doug Evans <dje@transmeta.com>
To: Dave Brolley <brolley@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Re: CGEN: RFA: Fast vs Full with scache-pbb
Date: Wed, 06 Sep 2000 13:37:00 -0000 [thread overview]
Message-ID: <14774.43800.665729.386324@casey.transmeta.com> (raw)
In-Reply-To: <39B51C99.3A2FC29C@redhat.com>
Dave Brolley writes:
> > It turns out that the call to <cpu>_pbb_begin in the generated
> > <cpu>_sem_x_begin was passing STATE_RUN_FAST_P (CPU_STATE
> > (current_cpu)) as the 'fast_p' argument. Now this flag will be 0
> > if -t is specified and 1 otherwise. However the rest of the
> > generated code (mloop.c, sem.c) is not set up for dynamic
> > fast/full switching (although it looks like some work was done
> > toward this goal in the past). As a result, only the 'sem_full'
> > function in the idesc_table is initialized for my build. Passing
> > fast_p==1 causes the semantic engine to attempt to use 'sem_fast'
> > function which is not initialized.
What do you mean by "dynamic fast/full switching".
next prev parent reply other threads:[~2000-09-06 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 11:53 Dave Brolley
2000-09-03 19:23 ` Ben Elliston
2000-09-05 9:17 ` Dave Brolley
2000-09-06 13:37 ` Doug Evans [this message]
2000-09-06 14:17 ` Dave Brolley
2000-09-06 14:45 ` Doug Evans
2000-09-08 11:19 ` Dave Brolley
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=14774.43800.665729.386324@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=brolley@redhat.com \
--cc=cgen@sources.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).