[M3devel] Compile Options

[Jay K]

aha, good reason to disable debugging.

I think this has been broken a very long time -- the usage says debugging is the default,
and that is true..and I see no way to disable it..

Either we need like -g0 or the default should be no symbols.
??

You can also hack the config files -- remove any -g(stabs)(+).
  An ok option for your immediate purposes, if not the right general solution for everyone.


I forgot to mention in my commit comment: I did go ahead with the m3back_debug, m3back_optimize switches.
It should be you just set m3back_debug = "" in the toplevel config (or maybe with -D on the command line?) no symbols.

Also more subtly I changed optimizing from -O3 to -O2 -Wuninitialized.
Maybe should leave that alone..as I almost never use it either way.


 - Jay

________________________________
> Date: Sun, 9 May 2010 21:51:05 +1000
> From: peter.mckinna at gmail.com
> To: hosking at cs.purdue.edu
> CC: m3devel at elegosoft.com
> Subject: Re: [M3devel] Compile Options
>
> Sorry should have mentioned AMD_64 linux. I was trying to check if the code generator was screwing up and every time I made a slight change the stabs were completely different in the 2 ms files from the same module. In fact the generated code was so completely different for just 2 lines of M3 I found it incomprehensible. I tried to turn off the debugging to reduce the clutter. So then I played around with some of the other compile time switches and found some problems. This is in version 5.8.4
>
>
> Regards
> Peter
>
> On Sat, May 8, 2010 at 2:55 PM, Tony Hosking> wrote:
>
> What target platform?
>
>
>
> On 8 May 2010, at 00:22, Peter McKinna wrote:
>
>
>
>> Hey,
>
>>
>
>> Using -c to disable library or program generation does not seem to work. Also how do you turn off debug symbol generation?
>
>> And the -O switch doesnt seem to optimise anything.
>
>>
>
>> Is it just me or the documentation.
>
>>
>
>> Regards
>
>>
>
>> Peter
>
>
>
>