From: Jody Bruchon <jody@jodybruchon.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 16:34:13 -0500 [thread overview]
Message-ID: <4F4BF6D5.7040801@jodybruchon.com> (raw)
In-Reply-To: <CAGc3vb0t3+vt0h2i6-hQObf1J=MBt1CN_LjPEcxnLDQZUJeNQg@mail.gmail.com>
On 02/27/12 15:42, Brad Normand wrote:
---snip---
> ACK is kind of a wildcard that might fit somewhere in-between any of
> this depending on what exactly it is, but we already know it has some
> issues. It does presumably work though.
I have read up on how ACK works, from some of the whitepapers on the
site. The 6502 code generator's output is absolutely nightmarish. ACK
apparently uses a not-so-grand intermediate representation that is
responsible for it not being that good at generating code.
> Writing our own toolchain... eech. Might have been a neat idea back
> in the 80's.
Where did all these other toolchains come from, anyway? As far as I am
aware (trust me, bcc is pretty hard to find solid information about),
the Dev86 toolchain was pretty much just Bruce Evans' work up until the
point that the Linux-8086 crew grabbed it and beefed it up further. It
might be yucky, but even if yucky, it's an option that would work.
Jody Bruchon
next prev parent reply other threads:[~2012-02-27 21:34 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 [this message]
2012-02-27 22:26 ` David Given
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=4F4BF6D5.7040801@jodybruchon.com \
--to=jody@jodybruchon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.