64 bit porting of JS
punsa
I am using JS 1.5 RC 6 codebase released in 2005. In recent
discussions, I got that Spidermonkey supports 64 bit platform (
http://groups.google.com/group/mozilla.dev.tech.js-engine/browse_thread/thread/d108545385160c52).
Even though I didn't get any specific document talking about support
of 64 bit platform architecture.
Now, I have tried compiling same code base over x86_64
architecture. Though, I am able to build it but with lot of
compilation warnings questioning its successful execution over a 64
bit platform. I am listing some of these warnings, which are specific
to 64 bit platforms.
jsarray.c:343: warning : cast from pointer to integer of different
size
jsarray.c:366: warning : cast from pointer to integer of different
size
jsarray.c:366: warning : cast from integer to pointer of different
size
jsarray.c:389: warning : cast from pointer to integer of different
size
jsarray.c:396: warning : cast from pointer to integer of different
size
jsarray.c:366: warning : cast from integer to pointer of different
size
jsarray.c:465: warning : cast from pointer to integer of different
size
Earlier, mail threads has talked about configure for building
JS over 64 but I am not sure about any specific I need to do for it.
But, when I checked jsautoconfig.h which is getting auto generated in
build has all types suitable for LP64 architecture which ever I need.
Is there other specific build parameter is required for building it
over 64 bit machine which can solve problem without code modification
which is discussed in earlier mail threads?
Regards Puneet
punsa
---------- Forwarded message ----------
From: punsa <engg.puneetsha...@gmail.com>
Date: Nov 16, 9:05 am
Subject: 64 bit porting of JS
To: mozilla.dev.tech.js-engine
Hi,
I am using JS 1.5 RC 6 codebase released in 2005. In recent
discussions, I got that Spidermonkey supports 64 bit platform (http://
groups.google.com/group/mozilla.dev.tech.js-engine/browse_thre...).
Another question I would like to ask about usage of 'int' in
structures, where it can cause alignment issues, for say structure not
aligned to 64, may lead to BUS error on unaligned pointer access. And
I have seen similar comment in jstypes.h for same, though below
comment suggest not to use JSUintn in structures, but is used in most
of cases. /
************************************************************************
** TYPES:
JSUintn ** JSIntn
** DESCRIPTION:
** The JSIntn types are most appropriate for automatic variables. They
are
** guaranteed to be at least 16 bits, though various architectures
may
** define them to be wider (e.g., 32 or even 64 bits). These types
are
** never valid for fields of a structure.
************************************************************************/
#if JS_BYTES_PER_INT >= 2
typedef int JSIntn;
typedef unsigned int JSUintn;
#else
#error
'sizeof(int)' not sufficient for platform use
#endif
Comments are expected. Thanks in advance.
Regards Puneet
