From: "Mike Frysinger" <vapier.adi@gmail.com>
To: David Given <dg@cowlark.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Writing compilers, and example.c vs compile-i386.c
Date: Mon, 16 Jun 2008 19:50:54 -0400 [thread overview]
Message-ID: <8bd0f97a0806161650w1d88f0d5k33601d66f3d3084@mail.gmail.com> (raw)
In-Reply-To: <4856F196.8020403@cowlark.com>
On Mon, Jun 16, 2008 at 7:04 PM, David Given wrote:
> I'm wanting to write a compiler-like tool that's capable of generating
> machine-code-like-stuff (don't ask, long story), and as such, have been
> looking around for C compiler front ends that will make my life easier.
> sparse looks extremely promising.
this may be worth investigating as well:
http://pcc.ludd.ltu.se/
-mike
next prev parent reply other threads:[~2008-06-16 23:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 23:04 Writing compilers, and example.c vs compile-i386.c David Given
2008-06-16 23:50 ` Mike Frysinger [this message]
2008-06-17 0:49 ` Christopher Li
2008-06-17 23:35 ` David Given
2008-06-18 0:41 ` Christopher Li
2008-06-20 23:46 ` David Given
2008-06-21 1:40 ` Christopher Li
2008-06-24 13:29 ` 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=8bd0f97a0806161650w1d88f0d5k33601d66f3d3084@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=dg@cowlark.com \
--cc=linux-sparse@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 NNTP newsgroup(s).