In the PE header there's a flag to indicate whether the binary is LargeAddressAware or not.
The PE header itself exists for both, *.exe and *.dll.
Is it really the case that Windows OS evaluates this flag for the parent executable, only?
Is it completely ignored for all DLL modules?
So why should i enable the LAA linker flag for DLLs if nobody is evaluating it?
I was having the following in mind:
Is there a way to force Windows issue a warning in case a LAA enabled exe loads a module that is not compiled as being LAA?
Also see related question: Drawbacks of using /LARGEADDRESSAWARE for 32 bit Windows executables?