9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fernan Bolando <fernanbolando@mailc.net>
To: 9fans@9fans.net
Subject: Re: [9fans] porting help please (gcc void pointer handling)
Date: Thu, 10 Sep 2009 00:27:41 +0800	[thread overview]
Message-ID: <1d5d51400909090927u2a4e6742k9614b79df841d3b6@mail.gmail.com> (raw)
In-Reply-To: <ace1f791830bf1d3f9d8c1e5cea17c14@terzarima.net>

On Thu, Sep 10, 2009 at 12:08 AM, Charles Forsyth<forsyth@terzarima.net> wrote:
> you might consider using a sed script to change the CT_.* style #defines,
> and run the sed script from the mkfile/makefile, so although the
> porting is (in your sense) `destructive' it's done by changing the
> original source file automatically. you could sed (say) from a .h.orig to a .h
> using a single rule.
>

I am trying to port nhc98 the bytecode haskell compiler.
I am hoping to avoid changing those definition because I think those
are generated by the
haskell compiler and then fed to the C compiler. So there are a whole
bunch of them.

If I change those and assuming everything works. Every time I use the
haskell compiler it will
generate the same style of codes and the same set of compile issue in
C compiler phase.

so I guess some sort of wrapper script for the pcc is easiest option.

thanks.

--
http://www.fernski.com



  parent reply	other threads:[~2009-09-09 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 15:03 Fernan Bolando
2009-09-09 15:35 ` erik quanstrom
2009-09-09 15:49   ` roger peppe
2009-09-10  9:30     ` Greg Comeau
2009-09-10  9:29   ` Greg Comeau
2009-09-10  9:40     ` erik quanstrom
2009-09-09 15:41 ` Charles Forsyth
     [not found] ` <1745bc1073a021783cf2ff8658d7ce47@quanstro.net>
2009-09-09 15:43   ` Fernan Bolando
2009-09-10  9:30     ` Greg Comeau
2009-09-09 16:08 ` Charles Forsyth
     [not found] ` <ace1f791830bf1d3f9d8c1e5cea17c14@terzarima.net>
2009-09-09 16:27   ` Fernan Bolando [this message]
2009-09-09 16:54     ` Charles Forsyth
2009-09-09 18:17     ` ron minnich
2009-09-11  1:45       ` Fernan Bolando
2009-09-10  9:31     ` Greg Comeau
2009-09-10  9:29 ` Greg Comeau

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=1d5d51400909090927u2a4e6742k9614b79df841d3b6@mail.gmail.com \
    --to=fernanbolando@mailc.net \
    --cc=9fans@9fans.net \
    /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).