From mboxrd@z Thu Jan  1 00:00:00 1970
From: Frank Cornelis <Frank.Cornelis@elis.ugent.be>
Subject: BCC software operations
Date: 04 Dec 2003 15:40:19 +0100
Sender: linux-8086-owner@vger.kernel.org
Message-ID: <1070548820.29047.9.camel@tom>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
List-Id: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: linux-8086@vger.kernel.org
Cc: Frank Cornelis <Frank.Cornelis@elis.ugent.be>

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