public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/25412] gfortran 4.0.2 seg fault Date: Sun, 05 Feb 2006 18:11:00 -0000 [thread overview] Message-ID: <20060205181112.28728.qmail@sourceware.org> (raw) In-Reply-To: <bug-25412-11880@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from fxcoudert at gcc dot gnu dot org 2006-02-05 18:11 ------- VASP is reported to compile fine with 4.1 and 4.2, and this audit trail doesn't have a self-contained code that exhibits the failure. Closing. -- fxcoudert at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25412
prev parent reply other threads:[~2006-02-05 18:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-14 15:20 [Bug fortran/25412] New: " gcc-bugzilla at gcc dot gnu dot org 2005-12-14 15:35 ` [Bug fortran/25412] " root at WPI dot EDU 2005-12-14 18:29 ` jb at gcc dot gnu dot org 2005-12-14 19:12 ` kargl at gcc dot gnu dot org 2005-12-14 19:20 ` fxcoudert at gcc dot gnu dot org 2006-02-05 15:43 ` pinskia at gcc dot gnu dot org 2006-02-05 18:11 ` fxcoudert at gcc dot gnu dot org [this message]
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=20060205181112.28728.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).