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/16861] segfault with doubly used module
Date: Tue, 19 Apr 2005 07:24:00 -0000	[thread overview]
Message-ID: <20050419072433.28843.qmail@sourceware.org> (raw)
In-Reply-To: <20040803172636.16861.yosef@phys.utb.edu>


------- Additional Comments From fxcoudert at gcc dot gnu dot org  2005-04-19 07:24 -------
Like comment #5 says, this one is not fixed. The patch I committed only adress
part of the issue. Removed patch keyword accordingly.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|patch                       |
   Last reconfirmed|2005-04-18 13:12:03         |2005-04-19 07:24:32
               date|                            |


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


  parent reply	other threads:[~2005-04-19  7:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-03 17:26 [Bug fortran/16861] New: gfortran compiler segfault yosef at phys dot utb dot edu
2004-08-03 17:28 ` [Bug fortran/16861] " yosef at phys dot utb dot edu
2004-08-03 17:31 ` yosef at phys dot utb dot edu
2004-08-03 17:34 ` yosef at phys dot utb dot edu
2004-08-03 18:12 ` reichelt at gcc dot gnu dot org
2004-08-03 21:20 ` pinskia at gcc dot gnu dot org
2004-09-08 19:15 ` toon at moene dot indiv dot nluug dot nl
2004-09-27 15:48 ` tobi at gcc dot gnu dot org
2004-10-01  3:23 ` [Bug fortran/16861] segfault with doubly used module pinskia at gcc dot gnu dot org
2004-11-09  5:35 ` dmitrym at acres dot com dot au
2004-12-02 10:38 ` paul dot richard dot thomas at cea dot fr
2005-01-15 17:13 ` pinskia at gcc dot gnu dot org
2005-01-18 13:11 ` coudert at clipper dot ens dot fr
2005-04-18 13:12 ` fxcoudert at gcc dot gnu dot org
2005-04-19  1:09 ` yosef at phys dot utb dot edu
2005-04-19  7:10 ` cvs-commit at gcc dot gnu dot org
2005-04-19  7:24 ` fxcoudert at gcc dot gnu dot org [this message]
2005-04-29 10:56 ` cvs-commit at gcc dot gnu dot org
2005-07-14 17:13 ` dje at gcc dot gnu dot org
2005-09-11 16:28 ` pault at gcc dot gnu dot org
2005-09-15 14:27 ` paul dot richard dot thomas at cea dot fr
2005-09-18  5:19 ` cvs-commit at gcc dot gnu dot org
2005-09-18 17:18 ` [Bug fortran/16861] [4.0 only] " pinskia at gcc dot gnu dot org
2005-09-18 20:02 ` pinskia at gcc dot gnu dot org
2005-09-18 20:27 ` pinskia at gcc dot gnu dot org
2005-09-23 17:16 ` cvs-commit 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=20050419072433.28843.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: 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).