From owner-diy_efi Mon Dec 12 17:28:34 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08277; Mon, 12 Dec 94 17:28:34 GMT Received: from relay.hp.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA08266; Mon, 12 Dec 94 12:28:29 -0500 Received: from hpmwtd.sr.hp.com by relay.hp.com with SMTP (1.37.109.14/15.5+ECS 3.3) id AA043793308; Mon, 12 Dec 1994 09:28:28 -0800 Received: from 65stang.sr.hp.com by hpmwtd.sr.hp.com with SMTP (15.11.1.6/15.5+ECS 3.3) id AA12744; Mon, 12 Dec 94 09:28:26 -0800 Received: by eagle.sr.hp.com (1.37.109.4/15.5+ECS 3.3) id AA03632; Mon, 12 Dec 94 09:28:20 -0800 From: Craig Eid Message-Id: <9412121728.AA03632@eagle.sr.hp.com> Subject: Re: OBDII compliance and Ford engines To: DIY_EFI Date: Mon, 12 Dec 1994 09:28:20 -0800 (PST) In-Reply-To: from "Ryan A Erickson" at Dec 12, 94 07:53:49 am X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 192 Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI The FORD 4.6 liter DOHC, 32 cam V-8 is OBDII compliant. -- Craig Eid Manufacturing Development Engineer Microwave Instruments Division, Hewlett Packard e-mail address craige@sr.hp.com From owner-diy_efi Mon Dec 12 17:45:00 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08333; Mon, 12 Dec 94 17:45:00 GMT Received: from scr.siemens.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA08328; Mon, 12 Dec 94 12:44:49 -0500 Received: from opsusa.sms.siemens.com (SYSTEM@[165.226.4.236]) by scr.siemens.com (8.6.8/8.6.6) with SMTP id MAA28828 for ; Mon, 12 Dec 1994 12:44:36 -0500 Message-Id: <199412121744.MAA28828@scr.siemens.com> Date: Mon, 12 Dec 1994 12:42 EST From: COOLEY@opsusa.sms.siemens.com (Dave, MR-TSE UPTIME Service Center Ext 2734) To: DIY_EFI Subject: J1850 multiplexed bus comm. X-Vms-To: SMTP%"DIY_EFI@coulomb.eng.ohio-state.edu" X-Vms-Cc: COOLEY Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hello, Just got to work and had a fax waiting from motorola. The J1850 bus interface is also manufactured by Motorola. The main interface chip is the "SC371016" this with a Harris HIP7020 bus converter ($2.00) and the MC68HC705C8 MCU will create the full interface. The bus speed of this system is 1Mb/sec, plenty fast for multiplexing different segments of the project. If anyone wants more specific info, Drop me a line and I will get copies of this paperwork sent out. Thanks, Dave Cooley cooldave@nando.net From owner-diy_efi Mon Dec 12 17:54:51 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08368; Mon, 12 Dec 94 17:54:51 GMT Received: from scr.siemens.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA08363; Mon, 12 Dec 94 12:54:45 -0500 Received: from opsusa.sms.siemens.com (SYSTEM@[165.226.4.236]) by scr.siemens.com (8.6.8/8.6.6) with SMTP id MAA29190 for ; Mon, 12 Dec 1994 12:54:19 -0500 Message-Id: <199412121754.MAA29190@scr.siemens.com> Date: Mon, 12 Dec 1994 12:52 EST From: COOLEY@opsusa.sms.siemens.com (Dave, MR-TSE UPTIME Service Center Ext 2734) To: DIY_EFI Subject: Postscript X-Vms-To: SMTP%"DIY_EFI@coulomb.eng.ohio-state.edu" X-Vms-Cc: COOLEY Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Hello.. Quick question... Is there a way to display the postscript files found here on a pc? Also, is there a way to print them on a Non-postscript printer (conversion utility to graphics) Thanks, Dave Cooley cooldave@nando.net From owner-diy_efi Mon Dec 12 18:06:21 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA08503; Mon, 12 Dec 94 18:06:21 GMT Received: from wotan.compaq.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA08498; Mon, 12 Dec 94 13:06:18 -0500 Received: from twisto.eng.hou.compaq.com by wotan.compaq.com with smtp (Smail3.1.28.1 #12) id m0rHF8d-000vIkC; Mon, 12 Dec 94 12:06 CST Received: from bangate.compaq.com by twisto.eng.hou.compaq.com with smtp (Smail3.1.28.1 #10) id m0rHF8Y-000uHzC; Mon, 12 Dec 94 12:06 CST Message-Id: Received: by bangate.compaq.com with VINES ; Mon, 12 Dec 94 12:06:13 CST Date: Mon, 12 Dec 94 12:03:32 CST From: Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com Subject: re: Postscript To: diy_efi Cc: Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI COOLEY@opsusa.sms.siemens.com (Dave, MR-TSE UPTIME Service Cent Wrote: | | | Hello.. |Quick question.. Is there a way to display the postscript files found here on | a pc? Also, is there a way to print them on a Non-postscript printer | (conversion utility to graphics) | Thanks, | Dave Cooley | cooldave@nando.net Cool Dave -- you can get ghostscript for DOS, which allows you to view and print postscript files, but I'm not sure where it is. It's an FSF thing, so you might try prep.ai.mit.edu. The FSF doesn't support DOS stuff, but there should be a pointer there to where you could get it. --steve From owner-diy_efi Mon Dec 12 22:41:27 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09656; Mon, 12 Dec 94 22:41:27 GMT Received: from curly.cc.swin.edu.au by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA09650; Mon, 12 Dec 94 17:41:14 -0500 Received: from romulus.mm.swin.edu.au by curly.cc.swin.edu.au (5.65c/1.34) id AA29960; Tue, 13 Dec 1994 09:41:09 +1100 Received: From MECHMAN/WORKQUEUE by romulus.mm.swin.edu.au via Charon-4.0-VROOM with IPX id 100.941213094102.480; 13 Dec 94 09:41:15 -1100 Message-Id: To: DIY_EFI From: "A.DENNISON -EN320/TEL.8296" Organization: Swinburne University Date: Tue, 13 Dec 1994 09:40:49 EST-11 Subject: (Fwd) (Commercial) HC11 C Compiler Priority: normal X-Mailer: WinPMail v1.0 (R1) Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Here is some information on a cheap HC11 compiler. There are two mailing lists on the HC11 if you want some more information. To subscribe: mail to: listserv@oberon.com subscribe robot-board mail to: listserv@bobcat.etsu.edu subscribe mc68hc11 ------- Forwarded Message Follows ------- Date: Thu, 15 Sep 1994 04:39:31 -0400 Reply-to: imagecft@netcom.com From: imagecft@netcom.com (Richard Man) To: Multiple recipients of list Subject: (Commercial) HC11 C Compiler Version 1.02 of the compiler is ready. Also note that there is now a mailing list for discussing icc11 and general HC11 programming issues. // richard ==== **** Professional HC11 Tools At a Budget Price! **** The ImageCraft HC11 C Compiler, ICC11, version 1.0 ICC11 is a high quality yet low cost compiler package that runs on DOS and OS2 environments. Included in the package are: . A comprehensive 90 page manual. . A fast near-ANSI C (*) conformant compiler with built-in peephole optimizer. . Quality code generation. Code size is typically only 5% to 20% larger than expensive ($500 to $1200) compilers. . Assembler, linker, and librarian. . Standard C header files and library functions. . HC11 specific support such as embedded assembly, pragma for declaring interrupt functions, etc. . Calling conventions compatible with other compilers. . Both 16 bit and 32 bit executables. . Technical support over the Internet, including a mailing list for discussions and product update information. . MIT Interactive C compatible multitasking kernel library. . Miniboard library. , Coming soon! Add-on low priced multitasking executive with subsumption architecture semantics. Price: $39.95, plus $3.95 shipping and handling within the U.S., $5.00 S&H to Canada and $10.00 overseas. CA residents please add 8 1/4% sales tax. To order, please send a check or money order (international orders may use a "postal" check in U.S. dollars) to: ImageCraft P.O.Box 64226 Sunnyvale, CA 94088-4226 (408) 749-0702 Please direct email inquires to: imagecft@netcom.com. To join the mailing list, send the message "subscribe icc11-list" to listserv@netcom.com. ---- (*) The following ANSI C features are not yet supported, but most are expected to be released at some future date: . Long data type is only 2 bytes, although limited 32 bit support is provided through typedef and library calls. . The compiler does not yet support floating point code generation. . A not quite full set of C library functions is supplied, but most of the missing functions are not applicable to embedded applications. . The preprocessor does not support trigraphs, and it only uses K & R macro rescanning rules. **** End ICC11 Announcement **** From owner-diy_efi Mon Dec 12 22:42:55 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09705; Mon, 12 Dec 94 22:42:55 GMT Received: from merlin.nando.net by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA09697; Mon, 12 Dec 94 17:42:51 -0500 Received: by merlin.nando.net (4.1/davel-nando/june94) id AA15718; Mon, 12 Dec 94 17:41:31 EST Date: Mon, 12 Dec 1994 17:41:30 -0500 (EST) From: David Cooley To: sdbartho@cca.rockwell.com Cc: DIY_EFI Subject: Re: Hello In-Reply-To: <9412121400.AA06753@star.cca.rockwell.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI On Mon, 12 Dec 1994 sdbartho@cca.rockwell.com wrote: > > >By 1998, all vehicles in the US have to be OBD_II compliant. > >Just a suggestion, but this will keep this project on top of technology! > > I read somewhere (think it was Hot Rod) that the OBD_II bill didn't pass > in the House. Did they finally push it through? Yes, It was passed. > > Another side effect of OBD_II was that all new ECMs were to be potted > so that tampering with the system would be difficult. I don't really like > the sound of this. The 94 and newer GM vehicles have Potted ECM's with Flash EEprom. It is the first step. Ford's have been like this for a while as have chrysller. Later, Dave > > Dig > sdbartho@hwking.cca.rockwell.com > Syclone/Typhoon mailing list. > Feel the power of the wind. > > From owner-diy_efi Mon Dec 12 22:41:33 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09661; Mon, 12 Dec 94 22:41:33 GMT Received: from shiva.trl.OZ.AU by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA09655; Mon, 12 Dec 94 17:41:21 -0500 Received: by shiva.trl.OZ.AU id AA14769 (5.65c/IDA-1.4.4 for DIY_EFI@coulomb.eng.ohio-state.edu); Tue, 13 Dec 1994 09:41:06 +1100 From: Craig Pugsley Message-Id: <199412122241.AA14769@shiva.trl.OZ.AU> Subject: Re: OBD-II To: DIY_EFI Date: Tue, 13 Dec 1994 09:41:06 +1100 (EST) In-Reply-To: from "Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com" at Dec 12, 94 10:27:13 am X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 871 Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI > | FYI: > | > | OBD-II = On-Board Diagnostics II > | > | (a system intended to indentify component and systems failures > | which prevent a vehicle from meeting emissions regulations) > | > | Anthony Tsakiris > | > > > It's more than that, it also defines a standard one or two wire serial bus > that the ECM uses to communicate with sensors and other equipment (including > diagnostic equipment), and a standard for the information packets that are > placed on the bus. So one diagnostic computer will work for all cars. This > would indeed be a good feature to include on a diy-efi computer. Is the 2 wire serial bus structure the same as the CAN bus developed by Bosch as a comms system for motor vehicles? Motorola have (according to the article) a 68HC705X4 with a CAN interface. Also according to the article it is different to the J1850 bus. Craig. From owner-diy_efi Mon Dec 12 23:06:10 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA09842; Mon, 12 Dec 94 23:06:10 GMT Received: from wotan.compaq.com by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA09837; Mon, 12 Dec 94 18:06:08 -0500 Received: from twisto.eng.hou.compaq.com by wotan.compaq.com with smtp (Smail3.1.28.1 #12) id m0rHJok-000vIrC; Mon, 12 Dec 94 17:06 CST Received: from bangate.compaq.com by twisto.eng.hou.compaq.com with smtp (Smail3.1.28.1 #10) id m0rHJog-000uI6C; Mon, 12 Dec 94 17:06 CST Message-Id: Received: by bangate.compaq.com with VINES ; Mon, 12 Dec 94 17:06:00 CST Date: Mon, 12 Dec 94 16:57:56 CST From: Steve=Ravet%Prj=Eng%PCPD=Hou@bangate.compaq.com Subject: re: Re: OBD-II To: diy_efi Cc: Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI Craig Pugsley Wrote: | Steve Ravet wrote: | > It's more than that, it also defines a standard one or two wire | serial bus | > that the ECM uses to communicate with sensors and other | equipment (including | > diagnostic equipment), and a standard for the information | packets that are | > placed on the bus. So one diagnostic computer will work for | all cars. This | > would indeed be a good feature to include on a diy-efi computer. | | Is the 2 wire serial bus structure the same as the CAN bus developed by | Bosch as a comms system for motor vehicles? Motorola have (according to | the article) a 68HC705X4 with a CAN interface. Also according to the | article it is different to the J1850 bus. | | Craig. | No. the single wire bus is based on GM's DLCS variable pulse width modulation, 10.4kbps. The two wire bus is based on Ford's HBCC bus, pulse width modulated, 41.6kbps. These are both laid out in SAE J1850. Outside the US, Bosch has developed CAN, which corresponds to ISO 9141. Peugot has developed another methond, called VAN, which does not appear to have been adopted by any standards committees. I don't have any details on the CAN bus, but it appears that it will only be used outside the US. This info is from the August 15 EDN Products Edition. -steve From owner-diy_efi Tue Dec 13 01:39:15 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA10644; Tue, 13 Dec 94 01:39:15 GMT Received: from merlin.nando.net by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA10639; Mon, 12 Dec 94 20:39:09 -0500 Received: by merlin.nando.net (4.1/davel-nando/june94) id AA20834; Mon, 12 Dec 94 20:37:21 EST Date: Mon, 12 Dec 1994 20:37:20 -0500 (EST) From: David Cooley To: Craig Pugsley Cc: DIY_EFI Subject: Re: OBD-II In-Reply-To: <199412122241.AA14769@shiva.trl.OZ.AU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI On Tue, 13 Dec 1994, Craig Pugsley wrote: > > | FYI: > > | > > | OBD-II = On-Board Diagnostics II > > | > > | (a system intended to indentify component and systems failures > > | which prevent a vehicle from meeting emissions regulations) > > | > > | Anthony Tsakiris > > | > > > > > > It's more than that, it also defines a standard one or two wire serial bus > > that the ECM uses to communicate with sensors and other equipment (including > > diagnostic equipment), and a standard for the information packets that are > > placed on the bus. So one diagnostic computer will work for all cars. This > > would indeed be a good feature to include on a diy-efi computer. > > Is the 2 wire serial bus structure the same as the CAN bus developed by > Bosch as a comms system for motor vehicles? Motorola have (according to > the article) a 68HC705X4 with a CAN interface. Also according to the > article it is different to the J1850 bus. > > Craig. > > Craig, It is very similar to the CAN bus, and the ISO9141-2 interface is one of the allowed 3 ways of communications for J1850. Dave From owner-diy_efi Tue Dec 13 02:52:25 1994 Received: by coulomb.eng.ohio-state.edu (920330.SGI/920502.SGI) id AA11026; Tue, 13 Dec 94 02:52:25 GMT Received: from localhost.eng.ohio-state.edu by coulomb.eng.ohio-state.edu via SMTP (920330.SGI/920502.SGI) for /usr/local/mail/majordomo-1.92/wrapper resend -p bulk -M 10000 -l Diy_Efi -f Diy_Efi-Owner -h coulomb.eng.ohio-state.edu -s -r DIY_EFI diy_efi-outgoing id AA11020; Mon, 12 Dec 94 21:52:20 -0500 Message-Id: <9412130252.AA11020@coulomb.eng.ohio-state.edu> To: diy_efi Subject: gcc port to 6811 :( Date: Mon, 12 Dec 94 21:52:20 -0500 From: John S Gwynne Sender: owner-diy_efi Precedence: bulk Reply-To: DIY_EFI -------- I took the time over this past weekend to build the Coactive gcc port for the 68hc11. I must say I'm not impressed with its output. Consider the following example: -------- cut here ------ int a[10]; main() { int i; for (i=0; i<10; i++) a[i]=i; } -------- cut here ------ The resulting code (with a -O; higher levels of optimization didn't do much better) is -------- cut here ------ 1 ;;;----------------------------------------- 2 ;;; Start MC6811 gcc assembly output 3 ;;; gcc compiler compiled on TBD 4 ;;; OPTIONS: -mlong_branch -mnogrom_lib optimize !strength_reduce 5 ;;; OPTIONS: peephole !omit_frame_pointer si gned-char 6 ;;; Source: t.c 7 ;;; Destination: /usr/tmp/cca10840.s 8 ;;; Compiled: Mon Dec 12 21:02:06 1994 9 ;;; (META)compiled by GNU C version 2.6.3. 10 ;;;----------------------------------------- 11 .area _CODE 12 .globl _main 0000 13 _main: 14 ;;;----------------------------------------- 15 ;;; PROLOGUE for main 16 ;;;----------------------------------------- 0000 18 3C 17 pshy ; Save stack frame 0002 18 30 18 tsy ; Set current stack frame 0004 DE 00 19 ldx *ZD1 0006 3C 20 pshx ; pushed register *ZD1 0007 DE 00 21 ldx *ZD2 0009 3C 22 pshx ; pushed register *ZD2 000A DE 00 23 ldx *ZD3 000C 3C 24 pshx ; pushed register *ZD3 000D DE 00 25 ldx *ZD4 000F 3C 26 pshx ; pushed register *ZD4 0010 DE 00 27 ldx *ZX1 0012 3C 28 pshx ; pushed register *ZX1 0013 DE 00 29 ldx *ZX2 0015 3C 30 pshx ; pushed register *ZX2 31 ;;;END PROLOGUE 0016 BD 00 00 32 jsr ___main ; CALL: (VOIDmode) ___main (0 bytes) 0019 CC 00 00 33 ldd #0 001C DD 00 34 std *ZD2 ; movhi: #0 -> *ZD2 001E CC 00 09 35 ldd #9 0021 DD 00 36 std *ZX2 ; movhi: #9 -> *ZX2 0023 CC 00 00 37 ldd #_a 0026 DD 00 38 std *ZD4 ; movhi: #_a -> *ZD4 0028 CC 00 01 39 ldd #1 002B DD 00 40 std *ZD3 ; movhi: #1 -> *ZD3 002D 41 L5: 002D DC 00 42 ldd *ZD2 002F DD 00 43 std *ZD1 ; movhi: *ZD2 -> *ZD1 0031 DC 00 44 ldd *ZD1 0033 05 45 asld 0034 DD 00 46 std *ZD1 ; ashlhi3: *ZD1 by #1 0036 DC 00 47 ldd *ZD1 0038 D3 00 48 addd *ZD4 003A DD 00 49 std *ZD1 ; addhi3: *ZD1 by *ZD4 003C DC 00 50 ldd *ZD1 003E DD 00 51 std *ZX1 ; movhi: *ZD1 -> *ZX1 0040 DC 00 52 ldd *ZD2 0042 DE 00 53 ldx *ZX1 0044 ED 00 54 std 0,x ; movhi: *ZD2 -> 0,x 0046 DC 00 55 ldd *ZD2 0048 D3 00 56 addd *ZD3 004A DD 00 57 std *ZD2 ; addhi3: *ZD2 by *ZD3 004C DC 00 58 ldd *ZD2 004E 1A 93 00 59 cpd *ZX2 ; cmphi *ZD2 with *ZX2 0051 2E 03 60 bgt .+5 0053 7E 00 2D 61 jmp L5 ; (ble) long branch 0056 38 62 pulx ; Pulling register *ZX2 0057 DF 00 63 stx *ZX2 0059 38 64 pulx ; Pulling register *ZX1 005A DF 00 65 stx *ZX1 005C 38 66 pulx ; Pulling register *ZD4 005D DF 00 67 stx *ZD4 005F 38 68 pulx ; Pulling register *ZD3 0060 DF 00 69 stx *ZD3 0062 38 70 pulx ; Pulling register *ZD2 0063 DF 00 71 stx *ZD2 0065 38 72 pulx ; Pulling register *ZD1 0066 DF 00 73 stx *ZD1 74 ;;;EPILOGUE 0068 18 38 75 puly ; Restore stack frame 006A 39 76 rts ; return from function 77 ;;;----------------------------------------- 78 ;;; END EPILOGUE for main 79 ;;;----------------------------------------- 80 .area _DATA 81 .globl _a 0000 82 _a: .blkb 20 83 ; END -------- cut here ------ For reference, the code between line 41 and 51 is only 3 instructions (L11: move.l %d0,(%a0); subq.w #4,%a0; dbra %d0,.L11) for the 68k (with a -O4) and that is with 32-bit integers and addresses. So, why does the hc11 port look so bad. First, the 68hc11 can not manage the frame pointer as expected by gcc; hence, all of the pulx/pshx instructions. Second, not enough 16-bit registers (double accumulators). This is made up for by "simulated" registers like ZD0, ZD1,... The result is not very impressive. Even when the int's are changed to 'signed char's (bytes)', by the time sign extension is applied for addressing (which uses ZD0 type registers...), the code is still not very impressive. Perhaps someone could post the output of ic11 for this program. Bottom line: I would not recommend gcc for the 68hc11; use a compiler better optimized for the hc11's architecture. In contrast, gcc works very well with the 68k family. John S Gwynne Gwynne.1@osu.edu _______________________________________________________________________________ T h e O h i o - S t a t e U n i v e r s i t y ElectroScience Laboratory, 1320 Kinnear Road, Columbus, Ohio 43212, USA Telephone: (614) 292-7981 * Fax: (614) 292-7292 -------------------------------------------------------------------------------