Skip to content

set the /LARGEADDRESSAWARE flag for Win32 builds#501

Closed
Kosta-Github wants to merge 1 commit into
cppcheck-opensource:masterfrom
Kosta-Github:Kosta/large_address_aware
Closed

set the /LARGEADDRESSAWARE flag for Win32 builds#501
Kosta-Github wants to merge 1 commit into
cppcheck-opensource:masterfrom
Kosta-Github:Kosta/large_address_aware

Conversation

@Kosta-Github

Copy link
Copy Markdown

This allows to have a larger address space and therefore more memory available for the 32-bit executables on 64-bit host systems on Windows.

For more details see: https://msdn.microsoft.com/en-us/library/wz223b1z.aspx

This allows to have a larger address space and therefore more memory available for the 32-bit executables on 64-bit host systems on Windows.

For more details see: https://msdn.microsoft.com/en-us/library/wz223b1z.aspx
@danmar

danmar commented Jan 24, 2015

Copy link
Copy Markdown
Collaborator

sounds good. i don't know much about windows development personally.

@PKEuS

PKEuS commented Jan 24, 2015

Copy link
Copy Markdown
Contributor

It should be <LargeAddressAware>true</LargeAddressAware>, not an additional flag.

@amaigil2

Copy link
Copy Markdown

Do you assume it is safe to do because cppcheck scans its own code? (and so should not perform incompatible pointer arithmetics)? Or because of extensive tests?

@PKEuS

PKEuS commented Jan 26, 2015

Copy link
Copy Markdown
Contributor

We do not require that pointers are smaller than 2 GB (cppcheck runs also on 64-bit systems).

PKEuS added a commit that referenced this pull request Jan 27, 2015
Idea from Kosta-Github (pull-request #501)
@PKEuS

PKEuS commented Jan 27, 2015

Copy link
Copy Markdown
Contributor

I adapted your changes and committed it: bfa16ec

I changed the way how /LARGEADDRESSAWARE is set and enabled it for all 32-bit configurations

@PKEuS PKEuS closed this Jan 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants