From: "David S. Miller" <davem@dm.cobaltmicro.com>
To: ultralinux@vger.kernel.org
Subject: Re: VIS
Date: Fri, 17 Jul 1998 12:34:10 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-90222358531054@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90222358531047@msgid-missing>
From: Andi Kleen <ak@muc.de>
Date: 17 Jul 1998 13:22:47 +0200
"David S. Miller" <davem@dm.cobaltmicro.com> writes:
> Not true at all, it depends upon how a port was done. The Sparc
> backend creates a situation where all use inline asm's are considered
> multi-instruction. GCC does not require this. And if this were
> changed, inline assembly could be scheduled just like anything else.
In theory it could be done (by specifying the function units in a fourth
column similar to what is done in the machine descriptions).
No, you just need to remove the classification of all asm's as
type attribute "multi", then any single insn asm can be moved around
and scheduled just like any other insn. In fact, if you wrote your
register constraints like a good little boy gcc will know how to
handle the dependencies right too (to deal with load latencies to an
input register used by your asm) etc.
It's totally trivial.
Later,
David S. Miller
davem@dm.cobaltmicro.com
next prev parent reply other threads:[~1998-07-17 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-16 12:23 VIS Sven Grundmann
1998-07-16 12:27 ` VIS David S. Miller
1998-07-16 13:12 ` VIS Sven Grundmann
1998-07-16 13:26 ` VIS David S. Miller
1998-07-16 23:37 ` VIS Andi Kleen
1998-07-17 3:58 ` VIS David S. Miller
1998-07-17 11:22 ` VIS Andi Kleen
1998-07-17 12:34 ` David S. Miller [this message]
1998-07-17 12:44 ` VIS Andi Kleen
1998-07-17 12:46 ` VIS David S. Miller
1998-07-17 13:29 ` VIS Andi Kleen
1998-07-17 13:42 ` VIS David S. Miller
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=marc-linux-ultrasparc-90222358531054@msgid-missing \
--to=davem@dm.cobaltmicro.com \
--cc=ultralinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.