public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at verizon dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/17423] gfortran segfault when compiling FM509.f from NIST testsuite Date: Sat, 11 Sep 2004 23:22:00 -0000 [thread overview] Message-ID: <20040911232202.28465.qmail@sourceware.org> (raw) In-Reply-To: <20040911222351.17423.jvdelisle@verizon.net> ------- Additional Comments From jvdelisle at verizon dot net 2004-09-11 23:21 ------- Using gdb with f951 I get the segfaults on the following programs from the NIST test suite: FM509.f trans-decl.c:1384 FM517.f trans-decl.c:1372 FM711.f trans-array.c:1619 FM903.f trans-array.c:1619 FM908.f trans-array.c:1619 FM909.f trans-array.c:1619 Test suite downloaded from: http://www.fortran-2000.com/ArnaudRecipes/fcvs21_f95.html 'modified' version used. Software is public domain, provide acknowledgement of NIST. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17423
next prev parent reply other threads:[~2004-09-11 23:22 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-11 22:23 [Bug fortran/17423] New: " jvdelisle at verizon dot net 2004-09-11 23:11 ` [Bug fortran/17423] " pinskia at gcc dot gnu dot org 2004-09-11 23:22 ` jvdelisle at verizon dot net [this message] 2004-09-12 0:53 ` bdavis at gcc dot gnu dot org 2004-09-12 0:56 ` pinskia at gcc dot gnu dot org 2004-11-10 2:45 ` jvdelisle at verizon dot net 2004-11-10 2:52 ` jvdelisle at verizon dot net 2004-12-11 5:59 ` jvdelisle at verizon dot net 2004-12-11 6:34 ` jvdelisle at verizon dot net 2005-01-06 14:41 ` tobi at gcc dot gnu dot org 2005-03-13 19:29 ` tobi at gcc dot gnu dot org 2005-04-30 17:57 ` pinskia at gcc dot gnu dot org 2005-05-07 22:16 ` jvdelisle at verizon dot net 2005-05-15 3:25 ` pinskia at gcc dot gnu dot org 2005-05-16 2:29 ` 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=20040911232202.28465.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).