POV-Ray : Newsgroups : povray.unix : Build optimisation flags? : Re: Build optimisation flags? Server Time
28 Jul 2024 08:23:51 EDT (-0400)
  Re: Build optimisation flags?  
From: Warp
Date: 23 Aug 2002 08:16:29
Message: <3d66279c@news.povray.org>
Roz <Rzl### [at] netscapenet> wrote:
> Strangely, it didn't make any difference. The file size is the same and
> the rendering times didn't really change. Perhaps the -s flag overrides
> the -g flag? Either way, it might as well not be there.

  Ah, I didn't notice that you had a -s flag as well. If I had, I would have
also said that "the -g is even more useless since you are removing all the
debugging information it produces with -s".
  AFAIK -s does not turn off -g, but it simply tells the linker to strip the
final binary. The compiler still adds the extra debugging information when
you specify -g (you can see this from the difference in size of the .o files).

  If -g does not have any negative effect in speed, then that's good. However,
it's still useless to specify it, and you only get a lot larger object files,
wasting your disk space.
  (Note that -s still makes a difference even when you don't specify -g; the
binary still has some debugging information which can be stripped; what -g
does is to add *extra* debugging information.)

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

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.