Thomas wrote:
> 
> > If you want to avoid the problem, your only solution is to get (access to) a
> > 64 bit system, that is any current Compaq Alpha, IBM Power, Sun Sparc, SGI
> > Mips or HP PA-RISC system and then recompile POV-Ray 3.1g for one of those (or
> > compatible systems).  Of course you can also wait for a final release of
> > POV-Ray 3.5 and compile its source code, but either way, a 32-bit processor is
> > simply not up to the data size you want to handle :-(
> 
> Unfortunatly radiosity doesn't work on 64 bit systems the last time I tried it. :(
> Pov 3.1 compile under AIX)

I just tested megapov 0.7 on a SGI PowerChallenge and it worked (including
radiosity) with gcc after some experiments with the compiler options.  

Numbers in text output were wrong and it crashed after the render but the
image was generated.  

I don't know much about 64 bit systems, but 3.1 is used quite often on
them so i don't think there are serious problems.  3.5 will of course have
to be tested in that concern, but i think it is already proved to be
running some platforms.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 21 Feb. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

> I just tested megapov 0.7 on a SGI PowerChallenge and it worked (including
> radiosity) with gcc after some experiments with the compiler options.
>
> Numbers in text output were wrong and it crashed after the render but the
> image was generated.
>
> I don't know much about 64 bit systems, but 3.1 is used quite often on
> them so i don't think there are serious problems.  3.5 will of course have
> to be tested in that concern, but i think it is already proved to be
> running some platforms.

Are you sure that you are running 64 bit? I've seen the weird numbers at the end as
well, sp probably you are. Maybe it has something to do with the size of pointers and
integers and stuff like that. As I understand that might be different on certain
platforms.

And as I said I tried pov 3.1 and not megapov and since there are changes in the
radiosity that might account for the difference as well.

Thomas

Post a reply to this message

Thomas <tho### [at] gmxnet> wrote:
> Are you sure that you are running 64 bit?

  This is a good question because at least when compiling for Sparc, gcc
does not support generating 64-bit code, but only 32-bit.
  The only compiler I know which can make 64-bit code for Sparc is the
Sun cc compiler.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

>   This is a good question because at least when compiling for Sparc, gcc
> does not support generating 64-bit code, but only 32-bit.
>   The only compiler I know which can make 64-bit code for Sparc is the
> Sun cc compiler.
>

I thought that there was a 64 bit version of Sparc Linux, that implies that
there is a 64 bit compiler as well i.e. GCC. The GCC version for PowerPC/Power
does generate 64 bit, but I used the IBM compiler.


Thomas

Post a reply to this message

Oopppps!!! That I ment to say is that 64 bit compiles of POV hav problems with
radiosity
on AIX. the 32 bit compile runs fine including radiosity. Most 64bit platforms are
capable of running 32 bit aplications (is this true for Alpha as well since that
always
was a 64 bit platform unlike some other systems that migrated from 32 to 64 bit???).

Thomas

Post a reply to this message

Warp wrote:
> 
> Thomas <tho### [at] gmxnet> wrote:
> > Are you sure that you are running 64 bit?
> 
>   This is a good question because at least when compiling for Sparc, gcc
> does not support generating 64-bit code, but only 32-bit.
>   The only compiler I know which can make 64-bit code for Sparc is the
> Sun cc compiler.

In general gcc should be able to generate 64 bit code, but i can't say for
sure if it does here, i also tried the original sgi cc but had some
problems.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 21 Feb. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

Maybe I should dig out the code and see whether a GCC compile would be any
better than a Xlc. Maybe something for next week.....

Thomas

Christoph Hormann wrote:

> Warp wrote:
> >
> > Thomas <tho### [at] gmxnet> wrote:
> > > Are you sure that you are running 64 bit?
> >
> >   This is a good question because at least when compiling for Sparc, gcc
> > does not support generating 64-bit code, but only 32-bit.
> >   The only compiler I know which can make 64-bit code for Sparc is the
> > Sun cc compiler.
>
> In general gcc should be able to generate 64 bit code, but i can't say for
> sure if it does here, i also tried the original sgi cc but had some
> problems.
>
> Christoph
>
> --
> POV-Ray tutorials, IsoWood include,
> TransSkin and more: http://www.tu-bs.de/~y0013390/
> Last updated 21 Feb. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

Christoph Hormann <chr### [at] gmxde> wrote:
> In general gcc should be able to generate 64 bit code, but i can't say for
> sure if it does here

  The 'file' utility (which is usually found in most unix systems) should
tell whether the executable binary is 64-bit or not.

  For example here:

warp@keisarikotka:~/temp/tmp>gcc3 -m64 test.c -o test
cc1: -m64 is not supported by this configuration
warp@keisarikotka:~/temp/tmp>gcc3 -mv9 test.c -o test
cc1: Invalid option `v9'
warp@keisarikotka:~/temp/tmp>gcc3 test.c -o test
warp@keisarikotka:~/temp/tmp>file ./test
./test:         ELF 32-bit MSB executable SPARC Version 1, dynamically linked, not
stripped
warp@keisarikotka:~/temp/tmp>cc -xarch=v9 test.c -o test
warp@keisarikotka:~/temp/tmp>file ./test                
./test:         ELF 64-bit MSB executable SPARCV9 Version 1, dynamically linked, not
stripped


-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp wrote:
> 
> > In general gcc should be able to generate 64 bit code, but i can't say for
> > sure if it does here
> 
>   The 'file' utility (which is usually found in most unix systems) should
> tell whether the executable binary is 64-bit or not.
> 
>   For example here:
> 
> [...]

Ok, it is only 32 bit, i tried options for 64, but it does not (yet) seem
to be supported for sgi.

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 21 Feb. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message

>   The 'file' utility (which is usually found in most unix systems) should
> tell whether the executable binary is 64-bit or not.

Cool, it even works on AIX, this is the output of my executable:

[veen@barium:~/private/povray31>file ./povray_pwr_64
./povray_pwr_64:        64-bit AIX executable or object module not stripped

Thomas

Post a reply to this message