x64 pitfalls to avoid

Question

4.00/5 (1 vote)

See more:

Hi all again.

I have read the articles by Karpov Andrey, but I would like more indepth pointers in regards to what not to use.
Example MSDN says that you should use DWORD_PTR / UINT_PTR / INT_PTR instead of DWORD / UINT / INT
and SetClassLongPTR and such.
Is there anything else I should start doing?
Like data types to avoid and those to use instead?

I am using VS2010 and I have the PVS-Studio trial installed. Are there any decent x64 static code analyzers?

Thanks in advance.

Posted 25-Jun-11 4:57am

ryan20fun

Updated 25-Jun-11 15:37pm

Deeksha Shenoy

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Espen Harlinn · Accepted Answer · 2011-06-25T05:35:00

Solution 1

Karpov Andrey seems to have covered most of it.

Just check that your solution does not require you to link against 32-bit only libraries; or has any other 32-bit interoperability requirements that will cause you a lot of grief.

Good luck,
Espen Harlinn

Posted 25-Jun-11 5:35am

Espen Harlinn

Comments

Sergey Alexandrovich Kryukov 25-Jun-11 18:49pm

I agree, this if most important, my 5.
Please see my solution on compatibility; MS Dependency Walker is a good tool.
--SA

Espen Harlinn 26-Jun-11 4:35am

Thank you, SAKryukov!

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-06-25T12:49:00

Solution 2

In addition the the library and what Espen says:

All three instruction-set architectures are incompatible in the sense that none two of them cannot be used is one process. I explain those architectures and compatibility aspects here:

How to use 32 bit DLL in 64 bit machine configuration.[^].

Microsoft Dependency Walker can help a lot, see http://en.wikipedia.org/wiki/Dependency_Walker[^], http://www.dependencywalker.com/[^].

—SA

Posted 25-Jun-11 12:49pm

Sergey Alexandrovich Kryukov

Comments

ryan20fun 26-Jun-11 2:18am

ok, will look at that.
so i maybe using 32bit and 64bit code together ?
doesnt the 64bit version get used instead ?

Sergey Alexandrovich Kryukov 26-Jun-11 11:31am

This is your choice bases on the considerations I explained.
The rule is: one process should be either x86 and use all x86 libraries, or it should be of instruction set architecture if your system (Itanium or x86-64, you have no choice here, only one of them), then all libraries should match.

The application can be of more then one process, working via IPC (say, via COM/DCOM), then each process should follow this rule, but some processes could be x86 (32-bit) and some of whatever*-64.

You choice depends on availability of all components for selected instruction-set architecture -- some may not be available for some architecture.
--SA

Espen Harlinn 26-Jun-11 4:37am

Good point - my 5

Sergey Alexandrovich Kryukov 26-Jun-11 11:25am

Thank you, Espen.
--SA