public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "billingd at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/39039] New: segfault with common block and "-O1 -ftree-vectorize -msse2" Date: Fri, 30 Jan 2009 04:49:00 -0000 [thread overview] Message-ID: <bug-39039-270@http.gcc.gnu.org/bugzilla/> (raw) The following program segfaults when compiled with "-O1 -ftree-vectorize -msse2". Compiler is gfortran trunk revision 143693 (4.4.0 20090127). Also fails with higher levels of optimization but requires both -ftree-vectorize and -msse2. program common real (kind=8) b(5) common /com1/b b = 100 end The case is reduced from gfortran.fortran-torture/execute/common.f90 -- Summary: segfault with common block and "-O1 -ftree-vectorize - msse2" Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: billingd at gcc dot gnu dot org GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39039
next reply other threads:[~2009-01-30 4:49 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-30 4:49 billingd at gcc dot gnu dot org [this message] 2009-01-30 9:56 ` [Bug target/39039] " ubizjak at gmail dot com
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-39039-270@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).