public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/18977] LAPACK test xeigtsts segfaults with optimization Date: Wed, 26 Jan 2005 17:23:00 -0000 [thread overview] Message-ID: <20050126172338.11681.qmail@sourceware.org> (raw) In-Reply-To: <20041214104244.18977.Thomas.Koenig@online.de> ------- Additional Comments From Thomas dot Koenig at online dot de 2005-01-26 17:23 ------- Here we go: $ cat sl-error.f implicit none real x(2,2) call foo(x) end subroutine foo(x) real x(2,2) real tmp(4), t16(4,4), btmp(4),temp DO 120 I = 1, 4 K = 5 - I TEMP = 1.0 / T16( K, K ) TMP( K ) = BTMP( K )*TEMP DO 110 J = K + 1, 4 TMP( K ) = TMP( K ) - ( TEMP*T16( K, J ) )*TMP( J ) 110 CONTINUE 120 CONTINUE X( 1, 1 ) = TMP( 1 ) X( 2, 1 ) = TMP( 2 ) X( 1, 2 ) = TMP( 3 ) X( 2, 2 ) = TMP( 4 ) end $ gfortran sl-error.f $ ./a.out $ gfortran -O1 sl-error.f $ ./a.out Segmentation fault $ gfortran -dumpmachine ia64-unknown-linux-gnu $ gfortran -v Using built-in specs. Configured with: ../gcc-4.0-20050123/configure --prefix=/home/zfkts --enable-languages=c,f95 Thread model: posix gcc version 4.0.0 20050123 (experimental) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18977
next prev parent reply other threads:[~2005-01-26 17:23 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-14 10:44 [Bug fortran/18977] New: LAPACK test xeigtsts segfaults Thomas dot Koenig at online dot de 2004-12-14 11:09 ` [Bug fortran/18977] LAPACK test xeigtsts segfaults with optimization Thomas dot Koenig at online dot de 2004-12-14 16:07 ` sgk at troutmask dot apl dot washington dot edu 2004-12-16 15:59 ` Thomas dot Koenig at online dot de 2004-12-17 9:30 ` Thomas dot Koenig at online dot de 2005-01-06 14:43 ` tobi at gcc dot gnu dot org 2005-01-06 15:43 ` giovannibajo at libero dot it 2005-01-06 15:46 ` pinskia at gcc dot gnu dot org 2005-01-06 17:01 ` Thomas dot Koenig at online dot de 2005-01-09 4:53 ` giovannibajo at libero dot it 2005-01-09 22:59 ` pbrook at gcc dot gnu dot org 2005-01-09 23:16 ` ebotcazou at gcc dot gnu dot org 2005-01-16 23:21 ` pbrook at gcc dot gnu dot org 2005-01-26 9:42 ` Thomas dot Koenig at online dot de 2005-01-26 10:00 ` steven at gcc dot gnu dot org 2005-01-26 15:26 ` Thomas dot Koenig at online dot de 2005-01-26 17:23 ` Thomas dot Koenig at online dot de [this message] 2005-01-26 19:08 ` sgk at troutmask dot apl dot washington dot edu 2005-01-26 19:46 ` [Bug target/18977] " Thomas dot Koenig at online dot de 2005-01-27 15:09 ` Thomas dot Koenig at online dot de 2005-01-27 15:25 ` [Bug target/18977] [4.0 regression] " Thomas dot Koenig at online dot de 2005-01-27 15:32 ` Thomas dot Koenig at online dot de 2005-01-27 15:33 ` pinskia at gcc dot gnu dot org 2005-01-28 13:48 ` Thomas dot Koenig at online dot de 2005-01-28 14:29 ` Thomas dot Koenig at online dot de 2005-02-01 11:13 ` giovannibajo at libero dot it 2005-02-01 21:32 ` wilson at tuliptree dot org 2005-02-12 16:29 ` wilson at gcc dot gnu dot org 2005-02-14 17:53 ` Thomas dot Koenig at online dot de 2005-02-15 16:20 ` wilson at gcc dot gnu dot org 2005-02-19 1:53 ` [Bug tree-optimization/18977] " wilson at gcc dot gnu dot org 2005-02-19 11:53 ` cvs-commit at gcc dot gnu dot org 2005-02-19 12:57 ` wilson 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=20050126172338.11681.qmail@sourceware.org \ --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).