Re: [9fans] porting help please (gcc void pointer handling)

[comeau@panix.com (Greg Comeau)]

In article <1d5d51400909090927u2a4e6742k9614b79df841d3b6@mail.gmail.com>,
Fernan Bolando <fernanbolando@mailc.net> wrote:
>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.

So I'll wager a wild guess that there is a #if/def that controls
whether the compiling C compiler is gcc or not?  IOWs, that may cause
it to emit a more standard form of the #define?

>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.

I'll go on another limb and wager even further that there is parens
-- or something -- mising from the #define in the first place.
(so instead of (void*)blah+99 this ((void*)(blah+99))) etc.
--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE ==>     http://www.comeaucomputing.com/tryitout
World Class Compilers:  Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?