public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/38431] New: [graphite] several ICEs with CP2K Date: Sat, 06 Dec 2008 19:31:00 -0000 [thread overview] Message-ID: <bug-38431-6642@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1496 bytes --] the current graphite branch segfaults & ICEs on several files from CP2K. Compiling with '-O2 -ffast-math -funroll-loops -ftree-vectorize -march=native -fgraphite -fgraphite-identity' To reproduce get http://www.pci.uzh.ch/vandevondele/tmp/CP2K_2008_12_03.tgz untar and type make at least on the following files: mltfftsg.F mltfftsg_tools.F harris_force_types.F ai_moments.F cp_units.F ps_wavelet_util.F cp_fm_basic_linalg.F ps_wavelet_kernel.F ai_angmom.F distribution_optimize.F qs_util.F atom_fit.F atom_operators.F dynamical_coeff_types.F pw_spline_utils.F pw_poisson_types.F xc_derivative_set_types.F cp_ddapc_methods.F qs_all_potential.F qs_operators_ao.F I have ICEs. The first one is: ai_moments.F: In function cossin: ai_moments.F:44: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. make: *** [ai_moments.o] Error The same files compile fine with '-O0 -fgraphite -fgraphite-identity' so I guess it is related to applying graphite to optimized code (or the other way around). -- Summary: [graphite] several ICEs with CP2K Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38431
next reply other threads:[~2008-12-06 19:31 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-06 19:31 jv244 at cam dot ac dot uk [this message] 2008-12-09 8:44 ` [Bug middle-end/38431] " jv244 at cam dot ac dot uk 2008-12-09 19:43 ` jv244 at cam dot ac dot uk 2008-12-09 20:12 ` [Bug middle-end/38431] [graphite] several ICEs with CP2K (summery) grosser at gcc dot gnu dot org 2008-12-09 20:26 ` grosser at gcc dot gnu dot org 2008-12-09 21:03 ` jv244 at cam dot ac dot uk 2008-12-09 21:12 ` jv244 at cam dot ac dot uk 2008-12-10 22:34 ` jv244 at cam dot ac dot uk 2008-12-11 19:20 ` jv244 at cam dot ac dot uk 2008-12-11 20:20 ` [Bug middle-end/38431] [graphite] several ICEs with CP2K (summary) jv244 at cam dot ac dot uk 2008-12-11 21:42 ` jv244 at cam dot ac dot uk 2008-12-13 8:41 ` jv244 at cam dot ac dot uk 2008-12-14 15:56 ` dominiq at lps dot ens dot fr 2008-12-15 17:32 ` jv244 at cam dot ac dot uk 2008-12-15 19:08 ` jv244 at cam dot ac dot uk 2008-12-15 19:45 ` jv244 at cam dot ac dot uk 2009-01-07 19:07 ` jv244 at cam dot ac dot uk 2009-01-07 19:23 ` sebpop at gmail dot com 2009-01-07 20:52 ` jv244 at cam dot ac dot uk 2009-01-08 17:11 ` spop at gcc dot gnu dot org 2009-01-08 19:31 ` jv244 at cam dot ac dot uk 2009-01-08 19:53 ` sebpop at gmail dot com 2009-01-09 5:38 ` jv244 at cam dot ac dot uk 2009-01-09 6:16 ` jv244 at cam dot ac dot uk 2009-01-09 6:18 ` jv244 at cam dot ac dot uk 2009-01-11 12:30 ` jv244 at cam dot ac dot uk 2009-01-11 12:59 ` jv244 at cam dot ac dot uk 2009-01-11 13:42 ` sebpop at gmail dot com 2009-01-13 19:52 ` Sebastian Pop 2009-01-13 19:53 ` sebpop at gmail dot com 2009-01-13 20:33 ` jv244 at cam dot ac dot uk 2009-01-13 21:57 ` Sebastian Pop 2009-01-13 21:57 ` sebpop at gmail dot com 2009-01-14 6:49 ` jv244 at cam dot ac dot uk 2009-01-14 10:20 ` Sebastian Pop 2009-01-14 10:20 ` sebpop at gmail dot com 2009-01-14 10:51 ` jv244 at cam dot ac dot uk 2009-01-14 12:09 ` jv244 at cam dot ac dot uk 2009-01-14 14:35 ` spop at gcc dot gnu dot org 2009-01-14 14:36 ` spop at gcc dot gnu dot org 2009-01-14 21:11 ` spop 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-38431-6642@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).