I downloaded the source for MegaPOV v0.7 so I could port it (like the
previous versions of MegaPOB) to OpenVMS.

The compile and link went fine, but...

In the following files...

	ISOFUNC.C
	LIGHTING.C
	PATTERN.C
	QUADRICS.C
	RADIOSIT.C
	SUPER.C
	VBUFFER.C

I got a error about "#pragma peephole off" not being known.

It linked without problems, and it ran and did render scenes
correctly.

My question, is "#pragma peephole off" needed?  Is this something
that was used for testing and not removed?

I would appreciate any input about this so I can finish my OpenVMS
port of this and get it out to the public :}

Thanks.

Post a reply to this message

Robert Byer wrote:
> 
> I downloaded the source for MegaPOV v0.7 so I could port it (like the
> previous versions of MegaPOB) to OpenVMS.
> 
> The compile and link went fine, but...
> 
> In the following files...
[Snip]
> I got a error about "#pragma peephole off" not being known.

Was it really error? Or was it warning? Unrecognized pragmas shouldn't
generate errors, they should be ignored by compiler (and user warned
about).

> It linked without problems, and it ran and did render scenes
> correctly.
> 
> My question, is "#pragma peephole off" needed?  Is this something
> that was used for testing and not removed?

I assume, that it was for turning peephole optimization off. Generally
pragmas give hints to compiler, so it is really not needed.
Probably someone tried various optimizations on some compiler and left
those pragmas in for some reason.

Post a reply to this message

In article <3A8917E3.848C7D35@mail.ourservers.net> , Robert Byer 
<bye### [at] mailourserversnet>  wrote:

> My question, is "#pragma peephole off" needed?  Is this something
> that was used for testing and not removed?

While I am in no way responsible for the code of MegaPOV, I can tell
what it is:  One current Mac compiler has a bug in its peephole
optimiser which causes an internal compiler error if some other
optimisations are on as well.  I guess someone added the pragma to the
source code to still get peephole optimisations in the other parts of
the code by leaving the global optimisation flag on.  Just remove it.


       Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:

> In article <3A8917E3.848C7D35@mail.ourservers.net> , Robert Byer 
> <bye### [at] mailourserversnet>  wrote:
> 
> > My question, is "#pragma peephole off" needed?  Is this something
> > that was used for testing and not removed?
> 
> While I am in no way responsible for the code of MegaPOV, I can tell
> what it is:  One current Mac compiler has a bug in its peephole
> optimiser which causes an internal compiler error if some other
> optimisations are on as well.  I guess someone added the pragma to the
> source code to still get peephole optimisations in the other parts of
> the code by leaving the global optimisation flag on.  Just remove it.
That someone was me (Yvo Smellenbergh).
Normally I remove those things in the sources but Nathan didn't complain
so I guess his compiler had no problem with it.
You can easely remove them, lets hope that we don't need them anymore
once CodeWarrior is updated!
Yvo Smellenbergh


-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

"smellenbergh" <sme### [at] skynetbe> wrote...
> Normally I remove those things in the sources but Nathan didn't complain
> so I guess his compiler had no problem with it.

Correct.  MS Visual C++ just ignored them with no warnings or errors.

-Nathan

Post a reply to this message

> 
> "smellenbergh" <sme### [at] skynetbe> wrote...
> > Normally I remove those things in the sources but Nathan didn't complain
> > so I guess his compiler had no problem with it.
> 
> Correct.  MS Visual C++ just ignored them with no warnings or errors.
>

Thanks for everyone's help, I just "#ifdef" them out for OpenVMS
compile, not
a problem.

Post a reply to this message