public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/38946] [4.4/4.5/4.6 Regression] gcc trunk 143562 - Testsuite - gfortran failing tests that worked previously
Date: Wed, 21 Jul 2010 09:09:00 -0000 [thread overview]
Message-ID: <20100721090913.4780.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38946-13830@http.gcc.gnu.org/bugzilla/>
------- Comment #36 from ro at gcc dot gnu dot org 2010-07-21 09:09 -------
Fixed on all active branches.
--
ro at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Known to fail|4.4.5 4.5.1 |
Known to work|4.6.0 |4.4.5 4.5.1 4.6.0
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38946
next prev parent reply other threads:[~2010-07-21 9:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 15:19 [Bug fortran/38946] New: " rob1weld at aol dot com
2009-01-23 20:04 ` [Bug fortran/38946] " mikael at gcc dot gnu dot org
2009-01-25 17:00 ` rob1weld at aol dot com
2009-01-25 17:35 ` rob1weld at aol dot com
2009-01-26 18:42 ` [Bug fortran/38946] [trunk regression] " mikael at gcc dot gnu dot org
2009-01-26 19:29 ` [Bug testsuite/38946] " pinskia at gcc dot gnu dot org
2009-01-27 15:50 ` rob1weld at aol dot com
2009-01-27 16:00 ` rob1weld at aol dot com
2009-01-27 19:38 ` [Bug testsuite/38946] [trunk regression]?gcc " DJ Delorie
2009-01-27 16:18 ` [Bug testsuite/38946] [trunk regression] gcc " rob1weld at aol dot com
2009-01-27 19:38 ` dj at redhat dot com
2009-01-27 22:29 ` rob1weld at aol dot com
2009-01-27 22:45 ` rob1weld at aol dot com
2009-01-27 23:26 ` rob1weld at aol dot com
2009-01-27 23:47 ` [Bug testsuite/38946] [4.4 Regression] " rob1weld at aol dot com
2009-01-29 12:32 ` rob1weld at aol dot com
2009-01-30 3:25 ` rob1weld at aol dot com
2009-02-01 13:21 ` rguenth at gcc dot gnu dot org
2009-04-21 16:02 ` [Bug testsuite/38946] [4.4/4.5 " jakub at gcc dot gnu dot org
2009-07-22 10:34 ` jakub at gcc dot gnu dot org
2009-10-15 12:55 ` jakub at gcc dot gnu dot org
2010-01-21 13:19 ` jakub at gcc dot gnu dot org
2010-04-30 9:01 ` [Bug testsuite/38946] [4.4/4.5/4.6 " jakub at gcc dot gnu dot org
2010-06-04 12:54 ` ro at gcc dot gnu dot org
2010-06-07 16:32 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-06-07 16:49 ` ro at gcc dot gnu dot org
2010-06-07 16:49 ` ro at gcc dot gnu dot org
2010-06-20 2:06 ` rob1weld at aol dot com
2010-06-25 18:56 ` ro at gcc dot gnu dot org
2010-06-25 19:25 ` jvdelisle at gcc dot gnu dot org
2010-06-25 19:26 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-06-25 20:21 ` jvdelisle at gcc dot gnu dot org
2010-06-25 20:34 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-06-25 20:42 ` jvdelisle at gcc dot gnu dot org
2010-06-25 20:43 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-06-25 21:33 ` jvdelisle at gcc dot gnu dot org
2010-07-09 19:18 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-20 18:46 ` rob1weld at aol dot com
2010-07-20 19:23 ` ro at gcc dot gnu dot org
2010-07-21 4:37 ` jvdelisle at gcc dot gnu dot org
2010-07-21 7:56 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-07-21 9:06 ` ro at gcc dot gnu dot org
2010-07-21 9:07 ` ro at gcc dot gnu dot org
2010-07-21 9:09 ` ro at gcc dot gnu dot org [this message]
2010-07-23 8:44 ` rob1weld at aol dot com
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=20100721090913.4780.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).