public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto correctly
Date: Tue, 30 May 2006 16:09:00 -0000	[thread overview]
Message-ID: <20060530160851.17202.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26106-682@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from hjl at lucon dot org  2006-05-30 16:08 -------
Tonto in SPEC CPU 2006 should work now with gcc 4.1 and 4.2.


-- 

hjl at lucon dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |27662
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
            Summary|[meta-bug] Gfortran can't   |[meta-bug] Gfortran can't
                   |compile tonto               |compile tonto correctly
Bug 26106 depends on bug 27662, which changed state.

Bug 27662 Summary: [4.1 only]: Transpose doesn't work on function return
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27662

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |
             Status|REOPENED                    |ASSIGNED

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


  parent reply	other threads:[~2006-05-30 16:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05 16:39 [Bug fortran/26106] New: Gfortran can't compile tonto hjl at lucon dot org
2006-02-05 16:41 ` [Bug fortran/26106] [meta-bug] " pinskia at gcc dot gnu dot org
2006-02-05 17:37 ` pinskia at gcc dot gnu dot org
2006-03-11 19:27 ` kargl at gcc dot gnu dot org
2006-03-11 20:15 ` hjl at lucon dot org
2006-03-15 16:53 ` pault at gcc dot gnu dot org
2006-03-15 17:26 ` kargl at gcc dot gnu dot org
2006-03-15 19:31 ` hjl at lucon dot org
2006-03-15 20:02 ` kargl at gcc dot gnu dot org
2006-03-15 20:18 ` hjl at lucon dot org
2006-03-15 20:42 ` kargl at gcc dot gnu dot org
2006-03-15 23:28 ` hjl at lucon dot org
2006-03-15 23:33   ` Andrew Pinski
2006-03-15 23:33 ` pinskia at physics dot uc dot edu
2006-03-16  0:14 ` hjl at lucon dot org
2006-03-16  5:08 ` pinskia at gcc dot gnu dot org
2006-04-10 15:07 ` paul dot richard dot thomas at cea dot fr
2006-04-13 13:36 ` paul dot richard dot thomas at cea dot fr
2006-04-13 13:48 ` hjl at lucon dot org
2006-04-13 13:49 ` hjl at lucon dot org
2006-04-19  4:59 ` pault at gcc dot gnu dot org
2006-04-20  6:21 ` jvdelisle at gcc dot gnu dot org
2006-04-20  6:25 ` jvdelisle at gcc dot gnu dot org
2006-04-22  4:48 ` jvdelisle at gcc dot gnu dot org
2006-05-30 16:09 ` hjl at lucon dot org [this message]
2006-07-30 23:27 ` [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto correctly hjl at lucon dot org
2006-08-10 12:11 ` paul dot richard dot thomas at cea dot fr
2006-08-10 16:40 ` hjl at lucon 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=20060530160851.17202.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).