From: Frank Cornelis <Frank.Cornelis@elis.ugent.be>
To: linux-8086@vger.kernel.org
Cc: Frank Cornelis <Frank.Cornelis@elis.ugent.be>
Subject: BCC software operations
Date: 04 Dec 2003 15:40:19 +0100 [thread overview]
Message-ID: <1070548820.29047.9.camel@tom> (raw)
Hi,
Why is bcc sometimes using software operations when there are hardware
instructions available? Avoiding calls to software implementations of
those operations can immensely speed up bcc generated code. It also
voids the endless copy&paste of the implementations of the helper
functions. BTW: Is someone still developing bcc? Is this the right
mailing-list for bcc related questions? Are there any bcc user guides?
Please CC me,
Frank.
--- softop.c.orig 1998-02-06 21:20:14.000000000 +0100
+++ softop.c 2003-12-04 15:27:24.000000000 +0100
@@ -219,7 +219,10 @@
{
case DIVOP:
#ifdef I8088
- call("idiv_");
+ //call("idiv_");
+ outnop1str("cwd");
+ outop2str("idiv\t");
+ outnregname(INDREG0);
#else
call("idiv");
#endif
reply other threads:[~2003-12-04 14:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1070548820.29047.9.camel@tom \
--to=frank.cornelis@elis.ugent.be \
--cc=linux-8086@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox