public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30399] testsuite failures in actual_array_constructor_2.f90 and actual_array_substr_2.f90
Date: Thu, 11 Jan 2007 22:54:00 -0000 [thread overview]
Message-ID: <20070111225417.14084.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30399-578@http.gcc.gnu.org/bugzilla/>
------- Comment #22 from ghazi at gcc dot gnu dot org 2007-01-11 22:54 -------
> However, I note that the commit to which you pointed, was made by me to
> trunk:
> http://gcc.gnu.org/ml/gcc-cvs/2006-07/msg00074.html
> The commit to 4.0 that introduced the testcases was made by aoliva at
> gcc dot gnu dot org in:
> http://gcc.gnu.org/ml/gcc-cvs/2006-07/msg00077.html
> From this I deduce that (i) the "unseen hands" were not mine and that
> (ii) It is perfectly safe to revert the testcases.
> Paul
> This gcc-cvs entry corresponds with what I see in the 4.0 branch; ie. no
> patch
I must have misread the svn archive, looks like you're right. I've ping'ed
Alexandre and if he cops to the error then I'll take care of removing the
testcases. And as I flasely blamed you for the problem I apologize!
Hopefully we can resolve this one way or another soon.
Thanks,
--Kaveh
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30399
next prev parent reply other threads:[~2007-01-11 22:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 23:31 [Bug fortran/30399] New: " ghazi at gcc dot gnu dot org
2007-01-07 1:22 ` [Bug fortran/30399] " ghazi at gcc dot gnu dot org
2007-01-07 1:24 ` ghazi at gcc dot gnu dot org
2007-01-07 1:40 ` ghazi at gcc dot gnu dot org
2007-01-07 9:10 ` ebotcazou at gcc dot gnu dot org
2007-01-07 21:15 ` pault at gcc dot gnu dot org
2007-01-09 3:19 ` ghazi at gcc dot gnu dot org
2007-01-09 9:42 ` pault at gcc dot gnu dot org
2007-01-09 15:13 ` ghazi at gcc dot gnu dot org
2007-01-09 15:24 ` ghazi at gcc dot gnu dot org
2007-01-10 0:03 ` danglin at gcc dot gnu dot org
2007-01-10 20:57 ` pault at gcc dot gnu dot org
2007-01-10 21:00 ` pault at gcc dot gnu dot org
2007-01-10 21:45 ` ghazi at gcc dot gnu dot org
2007-01-10 22:09 ` paulthomas2 at wanadoo dot fr
2007-01-11 6:33 ` jvdelisle at gcc dot gnu dot org
2007-01-11 7:10 ` ebotcazou at gcc dot gnu dot org
2007-01-11 7:28 ` ebotcazou at gcc dot gnu dot org
2007-01-11 7:46 ` jvdelisle at gcc dot gnu dot org
2007-01-11 17:05 ` ghazi at gcc dot gnu dot org
2007-01-11 17:16 ` ghazi at gcc dot gnu dot org
2007-01-11 19:29 ` paulthomas2 at wanadoo dot fr
2007-01-11 22:54 ` ghazi at gcc dot gnu dot org [this message]
2007-01-12 4:04 ` aoliva at gcc dot gnu dot org
2007-01-12 6:09 ` pault at gcc dot gnu dot org
2007-01-12 15:36 ` ghazi at gcc dot gnu dot org
2007-01-12 15:54 ` ghazi 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=20070111225417.14084.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).