This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/66070] New: cc1 gets killed by OOM killer
- From: "steffen at hauihau dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 08 May 2015 11:48:10 +0000
- Subject: [Bug tree-optimization/66070] New: cc1 gets killed by OOM killer
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66070
Bug ID: 66070
Summary: cc1 gets killed by OOM killer
Product: gcc
Version: 5.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: steffen at hauihau dot de
Target Milestone: ---
Created attachment 35496
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35496&action=edit
preprocessed source
Compiling a 32 bit version libaacplus 2.0.2 failed after some time because the
lto1 process for one of the ltrans portions gets killed by the kernel OOM
killer. I've then disabled LTO for the build and detected, that the cc1 process
compiling fram_gen.c gets also killed by the OOM killer. I went on by lastly
disabling graphite and the file compiled fine independent of LTO enabled or
disabled.
Here is the cmdline which leads to the OOM invocation (LTO disabled):
gcc -m32 -march=native -O2 -pipe -ggdb -floop-interchange -floop-strip-mine
-floop-block -ftree-loop-distribution -fira-loop-pressure -ftree-vectorize
-ftree-loop-linear -flto=5 -fuse-linker-plugin -fno-lto -c fram_gen.i -fPIC
-DPIC -o /dev/null
Please let me know if and how I can help you further.