Hi Alex,
thanks for reporting!
I'm not yet sure why our nightly testing does not catch this one.
Could you please try and report whether the following patch helps:
======== diff -r 006b01024195 MonetDB5/src/modules/mal/tokenizer.mx --- a/MonetDB5/src/modules/mal/tokenizer.mx Fri Sep 03 14:03:49 2010 +0200 +++ b/MonetDB5/src/modules/mal/tokenizer.mx Mon Sep 06 11:04:27 2010 +0200 @@ -148,7 +148,7 @@ #endif
#define COMP(h, d) ((h<<8)|(d&255)) -#define GET_d(x) ((x)&255) +#define GET_d(x) ((sht)((x)&255)) #define GET_h(x) ((x)>>8)
str ========
Thanks, Stefan
On Mon, Sep 06, 2010 at 01:45:10AM -0700, Alex Bo. wrote:
When using MONET_OID64=1 to build June10-SP1 on Windows 64, I get this in the MonetDB5 module:
.........\src\modules\mal\tokenizer.mx(562) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
How can I overcome this? (This did not happen with 32 bit OIDs)
Thanks.
View this message in context: http://old.nabble.com/Building-June10-SP1-64-with-64-OID-on-Windows-tp296323... Sent from the monetdb-users mailing list archive at Nabble.com.
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users