From: Fernan Bolando <fernanbolando@mailc.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] porting help please (gcc void pointer handling)
Date: Wed, 9 Sep 2009 23:03:32 +0800 [thread overview]
Message-ID: <1d5d51400909090803n4c4d5b7ewba9dfe0573d02495@mail.gmail.com> (raw)
On Wed, Sep 9, 2009 at 4:36 PM, Greg Comeau<comeau@panix.com> wrote:
> In article <1d5d51400909080844q1bee4c3s114ccc5e51ce52f5@mail.gmail.com>,
> Fernan Bolando <fernanbolando@mailc.net> wrote:
>>...error: initializer is not a constant: F0_Prelude_46primLeave
>>--h file ---
>>#define VAP_TAG 1
>>#define WORDSHIFT 5
>>#define WORDSIZE (1<<WORDSHIFT)
>>#define WORDMASK (WORDSIZE-1)
>>#define NS (WORDSIZE>>3)
>>#define ZAP_BIT (1L<<(WORDSIZE-1))
>>-- c file ----
>>unsigned F0_Prelude_46primLeave[] = {
>> CAPTAG(FN_Prelude_46primLeave,1)
>>#ifdef PROFILE
>>, useLabel(PROF_primLeave)
>>, 0
>>, 0
>>, 0
>>#endif
>
> The initializers to some things need to be constants.
> In your case, it appears that either CAPTAG or useLabel (or both)
> have ended up not being #define'd. Probably the header they are
> #define'd in is not being #include'd (you don't show it above,
> but then you don't show enough of your code to even reproduce it).
>
> On a relate note, you can see the results of preprocessing
> from pcc by using the -E and/or -P options, that way you
> can see whether the macro ended up getting substituted
> and what it was substituted to -- or not in your case.
> Some compilers also have options which will emit the trail of
> files #include'd but I don't see that option for pcc.
gcc happily compiles a definition like
#define CT_v249 ((void*)startLabel+464)
is it valid just to add to make the porting non-destructive?
#ifdef Plan9
#define void unsigned char
#endif
--
http://www.fernski.com
next reply other threads:[~2009-09-09 15:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 15:03 Fernan Bolando [this message]
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
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=1d5d51400909090803n4c4d5b7ewba9dfe0573d02495@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).