On 6/11/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
> Hi
>
> When you compile w/o debugging (i.e. with optimisation)
> the GCC spits whole-lotta stuff like that:
>
> tclthread.c:401: warning: dereferencing type-punned pointer will
> break strict-aliasing rules
> tclthread.c:401: warning: dere
I will need as much as possible speed for my next project where i will
use NS but i do not experience with gcc optimization either. But in
previous work i always wanted debugging info and sometimes -ON flags
messed with gdb because of optimization.
I say let's use -fno-strict-aliasing but use -fs
Am 11.06.2005 um 21:50 schrieb Vlad Seryakov:
I went through google about this and found out that many projects
like Linux, PostgreSQL and others use -fno-strict-aliasing. And
nobody could determine if this affects optimnization, so we can use
that flag as well and in the meantime slowly ch
I went through google about this and found out that many projects like
Linux, PostgreSQL and others use -fno-strict-aliasing. And nobody could
determine if this affects optimnization, so we can use that flag as well
and in the meantime slowly change the code.
Zoran Vasiljevic wrote:
Hi
When
Hi
I have tested the compilation on following platforms/os'es
Solaris(sparc) 2.6/2.8
Linux(intel) SuSE8.2/9.1
Mac OSX(powerpc) Darwin 6.8/7.9/8.0 (aka Mac OSX 10.2/10.3/10.4)
Next week we will finish the Windows port and there will be
some things changed as well
I have fixed some
Hi!
In case you miss some notification emails about my last
checkin, here is the reason:
Mailing [EMAIL PROTECTED]
Generating notification message...
Generating notification message... done.
Mailing [EMAIL PROTECTED]
Generating notification message...
Traceback (most recent call last):
File "/
Hi
When you compile w/o debugging (i.e. with optimisation)
the GCC spits whole-lotta stuff like that:
tclthread.c:401: warning: dereferencing type-punned pointer will
break strict-aliasing rules
tclthread.c:401: warning: dereferencing type-punned pointer will
break strict-aliasing rules
Th
