Memory Allocation Failure Due to Inappropriate Compiler Flags
From HPCBugBase
HPCBugBase Menu
Submit feedback
Overview
Index
- Defect types (defect patterns)
- Specific defects (individual defects that belong to a defect type)
- Instances (code examples)
- Articles (various info)
- Templates
- Show all categories
- Show all pages
Index by Languages
Contents |
[edit] Fault Description
On some machines you may not be able to get the full memory unless you compile with the "right" flags. There are also no warning signs that you are running out of memory until it happens. It is easy to fix once you know what the problem but really difficult to identify.
[edit] Statistics (Frequency)
- On IBM SP2, unless you use less-known obscure compilation flags, you only get 200MB per processor without warnings (as opposed to a desired 2GB memory.)
[edit] Other Findings and Contexts
Strictly speaking, an inappropriate choice of compiler flags is not a defect in the code unless, for example, these flags are written in build scripts such as Makefile.
|
Pages referring to this entry: Memory Allocation |
