32bit-64bit

问题 We have an old Perl application. Recently we moved to a new server which runs 64-bit Ubuntu. Old application uses pack/unpack functions and bitwise operations and now it fails because bitwise operations return 64-bit integers instead of 32-bit. Is there a way to force perl into 32-bit mode? If not, is there a way to install 32-bit perl on 64-bit machine? Thanks! 回答1: Is there a way to force perl into 32-bit mode? No, but you could switch to using the correct (portable) pack/unpack patterns

问题 I have few benchmark application complied for SPARC V8 32-bit architecture. I used them for performance evaluation of SPARC 32-bit processor. However, few application fall short of in performance. I want to test the performance with a 64-bit SPARC V9 architecture ( like OpenSPARC T1/T2). My question is will the compiled binaries for the 32-bit SPARC V8 architecture run in SPARC V9 architecture without any modifications? Are the binaries in both architectures compatible? 回答1: Presuming that

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . On 32-bit machines, reading and writing of 64-bit values in .net used to be non-atomic, i.e. when reading, I could read a value that had never been written to memory, consisting of one older 32-bit half, and one newer half. But are reads/writes atomic on 64-bit cpus? If so, does the (Windows) OS have to be 64-bit

问题 I'm working on a 64 bits application coded with .Net 4.0, C#. In this application, at some point, I need to start another exe file using the following code : l_process.StartInfo.FileName = _sFullFilePath; l_process.StartInfo.Verb = "Open"; l_process.StartInfo.CreateNoWindow = true; l_process.StartInfo.Arguments = l_sParams; l_process.Start(); Now, this external application being compiled under 32 bits environment (x86), I get the following error : **The specified executable is not valid for

问题 Got a problem with reading Excel files in C# The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine. , same for 'Microsoft.ACE.OLEDB.12.0' . that only occurs when I run my app on IIS. Running it locally on the machine where IIS is running works fine. The machine in question runs on Win2003 R2 Enterprise x64. I develop in VS2010, ASP.Net 4.0. It looks like there are 2 types of solutions to this problem: either install something (preferred) or switch to 32bit mode. I'd

问题 It seems that on 64-bit platforms it would be reasonable to have a 8-byte length prefix. If we can address more than 4Gb of mem why not allow, say, 5Gb strings? Is the answer just "by specification" or there is some interoperability/backwards compatibility reasons that I'm not aware of? Thanks. 回答1: The BSTR data type is the standard COM string data type. Changing the length prefix would make it impossible to safely move strings between processes of different bitness (or at least make it

问题 I have a Win32 application that makes ODBC-Connections. We connect using SQLDriverConnect() which displays a dialog to select the data source. In the x64-Version the Dialog shows and offers 2 different 32 Bit MS ACCESS Drivers. When i select one of these, in the 32 Bit version i would see a open file dialog to select a .mdb file. In the 64 Bit version the call to SQLDriverConnect() at this point returns with -1. SQLError() returns: "[Microsoft][ODBC Driver Manager] Data source name not found

问题 I'm trying to connect to a MS Access Database (.accdb file) via python. I used pyodbc to do this connection: import pyodbc conn = pyodbc.connect("DRIVER = {Microsoft Access Driver (*.mdb, *.accdb)}; DBG=C:\\test_db.accdb") However, I got the following error: ('IM002, '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)') I went to the ODBC Data Source Administrator and when I tried to configure or remove the Driver I got

问题 I just submitted an app update to the iOS AppStore with 64-bit and 32-bit compatibility. I haven't changed anything except the 64-bit architecture, however the app size is now almost doubled from a pre-64-bit size of 2.7 MB to 4.5 MB. Is this normal when compiling the app for both 64-bit and 32-bit iOS devices? Why does this happen (anyone care to explain in technical terms)? Or did something funky just happen in Xcode? 回答1: It's pretty normal because the code is compiled twice - once for 32

问题 I have a 64 bit RHEL host with 32 bit libraries installed. One vendor has a 32 bit .so I'd like to load into Python using ctypes. from ctypes import CDLL CDLL('32bitdinosaur.so') OSError: 32bitdinosaur.so: wrong ELF class: ELFCLASS32 Of course 64 bit libraries are OK. Eg: CDLL('libc.so.6') Works fine. 回答1: It looks like the best way to do this is to have a 32 bit python in a separate process load the .so, and call the 32 bit python from a 64 bit Python. 来源： https://stackoverflow.com/questions