public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tobi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/15080] Forall bounds not calculated correctly (forall_3.f90)
Date: Mon, 09 May 2005 12:09:00 -0000	[thread overview]
Message-ID: <20050509120521.16161.qmail@sourceware.org> (raw)
In-Reply-To: <20040422212419.15080.pbrook@gcc.gnu.org>


------- Additional Comments From tobi at gcc dot gnu dot org  2005-05-09 12:05 -------
Are you going to review that patch, Paul?  I don't think anybody else is qualified.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tobi at gcc dot gnu dot org


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


  parent reply	other threads:[~2005-05-09 12:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 21:54 [Bug fortran/15080] New: [gfortran] " pbrook at gcc dot gnu dot org
2004-04-22 22:05 ` [Bug fortran/15080] " pbrook at gcc dot gnu dot org
2004-12-27 17:22 ` [Bug fortran/15080] " tobi at gcc dot gnu dot org
2004-12-27 17:24 ` pinskia at gcc dot gnu dot org
2004-12-27 17:37 ` tobi at gcc dot gnu dot org
2004-12-27 17:41 ` pbrook at gcc dot gnu dot org
2005-01-06 14:37 ` tobi at gcc dot gnu dot org
2005-01-08 22:28 ` pinskia at gcc dot gnu dot org
2005-02-28 15:49 ` amodra at bigpond dot net dot au
2005-03-08 15:35 ` Thomas dot Koenig at online dot de
2005-03-08 20:30 ` Thomas dot Koenig at online dot de
2005-04-29 12:18 ` jakub at gcc dot gnu dot org
2005-04-29 15:20 ` jakub at gcc dot gnu dot org
2005-05-09 12:09 ` tobi at gcc dot gnu dot org [this message]
2005-05-15 21:37 ` aj at gcc dot gnu dot org
2005-05-15 21:42 ` pbrook at gcc dot gnu dot org
2005-05-17  6:32 ` cvs-commit at gcc dot gnu dot org
2005-05-17  7:02 ` cvs-commit at gcc dot gnu dot org
2005-05-17 11:26 ` 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=20050509120521.16161.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).