On 11/16/2012 4:05 PM, john skaller wrote:
> I have vague idea: if you're using "the very latest gcc" with -O2 or higher
> optimisation -- your code (and Judy) are not ISO compliant, they break
> strict aliasing rules. Later versions of gcc actually use this rule for
> optimisation.
>
> The rule says type punning is not allowed. So this means pointer
> casts are always wrong, other than two and fro with void*.
> I found my code broke apart on Linux where I have a later version
> of gcc than on my Mac, so I had to turn on -fnostrict-aliasing with -O2.
Hmm... I'm not running with any optimizations.

Did you run this with your own Win64 port of the Judy code, or did you 
use the version that Pradeep posted last month?


Tim

------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Judy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/judy-devel

Reply via email to