public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read Date: Sat, 21 Jan 2006 07:21:00 -0000 [thread overview] Message-ID: <20060121072115.15776.qmail@sourceware.org> (raw) In-Reply-To: <bug-25697-10129@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from jvdelisle at gcc dot gnu dot org 2006-01-21 07:21 ------- Subject: Bug 25697 Author: jvdelisle Date: Sat Jan 21 07:21:11 2006 New Revision: 110062 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110062 Log: 2006-01-20 Jerry DeLisle <jvdelisle@gcc.gnu.org> PR fortran/25697 * gfortran.dg/read_eof.f90: New test. Added: branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/read_eof.f90 Modified: branches/gcc-4_1-branch/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697
next prev parent reply other threads:[~2006-01-21 7:21 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-06 18:24 [Bug libfortran/25697] New: " dir at lanl dot gov 2006-01-06 20:11 ` [Bug libfortran/25697] " dir at lanl dot gov 2006-01-07 0:59 ` jvdelisle at gcc dot gnu dot org 2006-01-08 9:40 ` jvdelisle at gcc dot gnu dot org 2006-01-09 1:53 ` dir at lanl dot gov 2006-01-09 5:27 ` jvdelisle at gcc dot gnu dot org 2006-01-09 18:18 ` dir at lanl dot gov 2006-01-11 3:45 ` jvdelisle at gcc dot gnu dot org 2006-01-11 15:34 ` dir at lanl dot gov 2006-01-11 16:02 ` dir at lanl dot gov 2006-01-11 16:50 ` dir at lanl dot gov 2006-01-12 6:46 ` jvdelisle at gcc dot gnu dot org 2006-01-18 6:21 ` jvdelisle at gcc dot gnu dot org 2006-01-18 6:23 ` jvdelisle at gcc dot gnu dot org 2006-01-18 6:41 ` jvdelisle at gcc dot gnu dot org 2006-01-18 6:42 ` jvdelisle at gcc dot gnu dot org 2006-01-21 7:19 ` jvdelisle at gcc dot gnu dot org 2006-01-21 7:21 ` jvdelisle at gcc dot gnu dot org [this message] 2006-01-25 7:41 ` jvdelisle 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=20060121072115.15776.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).