From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Given Subject: Re: SDCC porting feasibility study, part 1: the assembler Date: Mon, 27 Feb 2012 22:26:15 +0000 Message-ID: <4F4C0307.3060306@cowlark.com> References: <20120227100515.GE27951@vega.lgb.hu> <4F4BA549.10506@jodybruchon.com> <4F4BD0D2.7030005@cowlark.com> <4F4BDB5D.6000304@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig37E752022A41880233C816DC" Return-path: In-Reply-To: <4F4BDB5D.6000304@gmail.com> Sender: linux-8086-owner@vger.kernel.org List-ID: To: "ELKS (linux-8086)" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig37E752022A41880233C816DC Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 27/02/12 19:37, Harley Laue wrote: [...] > I was barely able to even get this one to compile on my host machine. I= t > seems they don't have very good support for 64bit Linux. Once it was > compiled the ack command (for instance) had no usage help message as fa= r > as I could tell. Overall, it didn't leave a very good taste in my mouth= =2E Yeah, I got fairly burnt out working on it --- it's a massive chunk of code and simply coming to terms with the build system was incredibly hard work. (I eventually had to *write my own build tool* to make it build. Sigh.) The 64 bit issues basically stem from the fact that it comes from another era and it doesn't understand longs that are 64 bits wide. I have a fix that seems to work. I just don't understand *why* it works, which is why it's not checked in. =2E..also, I've just discovered this piece of code: vprint(fmt,p1,p2,p3,p4,p5,p6,p7) char *fmt ; { /* Diagnostic print, no auto NL */ fprintf(STDOUT,fmt,p1,p2,p3,p4,p5,p6,p7); } *shudder* As I said, another era. As for documentation --- there should be man pages for pretty much everything, although I am aware that some of the more exotic stuff (like the assemblers) haven't made it to the release package. If anyone's interested, I can have another go at making it work on 64-bit machines. I think the output code is better than bcc's, but it's been a while since I've seen the output. (The 8086 backend has had a fair bit of work done to it.) --=20 =E2=94=8C=E2=94=80=E2=94=80=E2=94=80 =EF=BD=84=EF=BD=87=EF=BC=A0=EF=BD=83= =EF=BD=8F=EF=BD=97=EF=BD=8C=EF=BD=81=EF=BD=92=EF=BD=8B=EF=BC=8E=EF=BD=83=EF= =BD=8F=EF=BD=8D =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 http://www.= cowlark.com =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 =E2=94=82 =E2=94=82 "Never attribute to malice what can be adequately explained by =E2=94=82 stupidity." --- Nick Diamos (Hanlon's Razor) --------------enig37E752022A41880233C816DC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPTAMJf9E0noFvlzgRAnL3AKCHpYaKe2EONck+YUG/sPZv82HAaQCfdWCo fvmGwMRcQKUIajuhbbmV+8E= =WcMg -----END PGP SIGNATURE----- --------------enig37E752022A41880233C816DC--