public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30084] segmentation falut when compiling certain code
Date: Wed, 20 Dec 2006 12:24:00 -0000	[thread overview]
Message-ID: <20061220122419.19646.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30084-12424@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pault at gcc dot gnu dot org  2006-12-20 12:24 -------
Note the patch was submitted 19/12 but the tracking system seems to have lost
it.

Paul


-- 

pault at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |pault at gcc dot gnu dot org
                   |dot org                     |
             Status|NEW                         |ASSIGNED
   Last reconfirmed|2006-12-06 22:39:44         |2006-12-20 12:24:19
               date|                            |


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


  parent reply	other threads:[~2006-12-20 12:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 14:33 [Bug fortran/30084] New: " trumsko at yahoo dot com
2006-12-06 14:36 ` [Bug fortran/30084] " trumsko at yahoo dot com
2006-12-06 17:38 ` kargl at gcc dot gnu dot org
2006-12-06 22:40 ` burnus at gcc dot gnu dot org
2006-12-07 16:30 ` pault at gcc dot gnu dot org
2006-12-20 12:24 ` pault at gcc dot gnu dot org [this message]
2006-12-21 16:18 ` [Bug fortran/30084] segmentation fault " burnus at gcc dot gnu dot org
2006-12-22 20:49 ` pault at gcc dot gnu dot org
2006-12-27  2:36 ` [Bug fortran/30084] [4.2 and 4.1 only] " pinskia at gcc dot gnu dot org
2007-01-03 21:27 ` pault at gcc dot gnu dot org
2007-01-03 21:30 ` [Bug fortran/30084] [4.1 " pault at gcc dot gnu dot org
2007-01-10 19:07 ` 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=20061220122419.19646.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).