From: David Given <dg@cowlark.com>
To: "ELKS (linux-8086)" <linux-8086@vger.kernel.org>
Subject: Re: SDCC porting feasibility study, part 1: the assembler
Date: Mon, 27 Feb 2012 22:26:15 +0000 [thread overview]
Message-ID: <4F4C0307.3060306@cowlark.com> (raw)
In-Reply-To: <4F4BDB5D.6000304@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
On 27/02/12 19:37, Harley Laue wrote:
[...]
> I was barely able to even get this one to compile on my host machine. It
> 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 far
> as I could tell. Overall, it didn't leave a very good taste in my mouth.
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.
...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.)
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
prev parent reply other threads:[~2012-02-27 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 0:18 SDCC porting feasibility study, part 1: the assembler Brad Normand
2012-02-27 10:05 ` Gábor Lénárt
2012-02-27 15:43 ` Brad Normand
2012-02-27 15:46 ` Jody Bruchon
2012-02-27 17:53 ` Brad Normand
2012-02-27 18:52 ` David Given
2012-02-27 19:04 ` Chad
2012-02-27 19:33 ` Brad Normand
2012-02-27 19:37 ` Harley Laue
2012-02-27 20:42 ` Brad Normand
2012-02-27 21:34 ` Jody Bruchon
2012-02-27 22:26 ` David Given [this message]
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=4F4C0307.3060306@cowlark.com \
--to=dg@cowlark.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).