public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/52307] New: Segmentation fault in Lapack with -O3 -floop-flatten -floop-strip-mine
Date: Sun, 19 Feb 2012 01:57:00 -0000	[thread overview]
Message-ID: <bug-52307-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52307

             Bug #: 52307
           Summary: Segmentation fault in Lapack with -O3 -floop-flatten
                    -floop-strip-mine
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: tkoenig@gcc.gnu.org
                CC: rguenth@gcc.gnu.org


Running the Lapack tests (and looking at PR 50561), I encountered this:

 All tests for SPP drivers  passed the threshold (   1910 tests run)

 SPB routines passed the tests of the error exits

Program received signal 11 (SIGSEGV): Segmentation fault.

Backtrace for this error:
  + [0xfff8e340418]
  + function 0000009f.plt_call.cosf@@GLIBC_2.3+0 (0x100B6FDC)
    from file crtstuff.c

tkoenig@gcc1-power7 TESTING]$ ~/bin/gfortran -v
Using built-in specs.
COLLECT_GCC=/home/tkoenig/bin/gfortran
COLLECT_LTO_WRAPPER=/home/tkoenig/libexec/gcc/powerpc64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: powerpc64-unknown-linux-gnu
Configured with: ../trunk/configure --prefix=/home/tkoenig
--enable-languages=c,fortran --with-ppl --with-cloog
Thread model: posix
gcc version 4.7.0 20120218 (experimental) [trunk revision 184372] (GCC)
[tkoenig@gcc1-power7 TESTING]$

This is after the fix for PR 50561, and may be related.

I haven't yet checked if this is a regression.


             reply	other threads:[~2012-02-19  1:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19  1:57 tkoenig at gcc dot gnu.org [this message]
2012-02-19  9:33 ` [Bug tree-optimization/52307] " tkoenig at gcc dot gnu.org
2012-02-19 12:24 ` dominiq at lps dot ens.fr
2012-02-19 12:27 ` dominiq at lps dot ens.fr
2012-02-19 13:34 ` dominiq at lps dot ens.fr
2012-02-19 14:19 ` dominiq at lps dot ens.fr
2012-02-19 14:30 ` dominiq at lps dot ens.fr
2012-02-26 12:35 ` tkoenig at gcc dot gnu.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-52307-4@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: link
Be 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).