public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/31280] New: segfault in remove_referenced_var Date: Tue, 20 Mar 2007 15:51:00 -0000 [thread overview] Message-ID: <bug-31280-9711@http.gcc.gnu.org/bugzilla/> (raw) Seeing the following with mainline using -O2 -ftree-loop-linear when building galgel benchmark from cpu2000. I couldn't whittle down to a single testcase so will attatch both source files. 178.galgel/run> /home/pthaugen/install/gcc/trunk/bin/gfortran -c -m64 -ffixed-form -O2 -ftree-loop-linear modules.f90 178.galgel/run> /home/pthaugen/install/gcc/trunk/bin/gfortran -c -m64 -ffixed-form -O2 -ftree-loop-linear sysnsL.f90 sysnsL.f90: In function #sysnsl#: sysnsL.f90:6: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. (gdb) run Starting program: /home/pthaugen/install/gcc/trunk/libexec/gcc/powerpc64-linux/4.3.0/f951 sysnsL.f90 -quiet -dumpbase sysnsL.f90 -m64 -auxbase sysnsL -O2 -version -ffixed-form -ftree-loop-linear -fintrinsic-modules-path /home/pthaugen/install/gcc/trunk/lib/gcc/powerpc64-linux/4.3.0/finclude -o sysnsL.s GNU F95 version 4.3.0 20070314 (experimental) (powerpc64-linux) compiled by GNU C version 4.1.0 (SUSE Linux). GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 Program received signal SIGSEGV, Segmentation fault. remove_referenced_var (var=<value optimized out>) at /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-dfa.c:771 771 ggc_free (*loc); (gdb) bt 5 #0 remove_referenced_var (var=<value optimized out>) at /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-dfa.c:771 #1 0x103d1238 in remove_unused_locals () at /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-live.c:518 #2 0x1026f204 in execute_function_todo (data=<value optimized out>) at /home/pthaugen/src/gcc/trunk/gcc/gcc/passes.c:865 #3 0x1026ee44 in do_per_function (callback=0x1026efe0 <execute_function_todo>, data=0x21) at /home/pthaugen/src/gcc/trunk/gcc/gcc/passes.c:757 #4 0x1026ef4c in execute_todo (flags=33) at /home/pthaugen/src/gcc/trunk/gcc/gcc/passes.c:935 (More stack frames follow...) -- Summary: segfault in remove_referenced_var Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pthaugen at us dot ibm dot com GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31280
next reply other threads:[~2007-03-20 15:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-20 15:51 pthaugen at us dot ibm dot com [this message] 2007-03-20 15:53 ` [Bug tree-optimization/31280] " pthaugen at us dot ibm dot com 2007-03-20 17:34 ` pinskia at gcc dot gnu dot org 2007-03-20 18:09 ` pthaugen at us dot ibm dot com 2007-03-20 18:10 ` pthaugen at us dot ibm dot com 2007-03-29 0:41 ` pinskia at gcc dot gnu dot org 2007-06-22 8:40 ` spop at gcc dot gnu dot org 2009-01-02 5:56 ` [Bug tree-optimization/31280] [4.3 Regression] " pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31280-9711@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).