public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michelin60 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase
Date: Fri, 31 Aug 2007 01:44:00 -0000	[thread overview]
Message-ID: <20070831014351.26014.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33252-14842@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from michelin60 at gmail dot com  2007-08-31 01:43 -------
(In reply to comment #5)
> First off don't CC anyone unless there is a real reason to like you know they
> caused the issue.  Second most of the rest of the failures are PR 33225
> anyways.
> 
First of all I CC'd Dr. Edelsohn because I mentioned him and he was the acting
on PR33168, you chimed in about 24 hours later. Even you mention somebody
involved by name it is common curtesy to make that person aware of that
mention. 

Second I mentioned Mark Mitchell because he, as relesae manager, put a stop to
backporting
definitely aggravating productive use of GCC.

Third you mentioning PR33168 out of context instead of PR33225 was just plain
dumb so I CC'd Burnus because he seems to be working pretty hard to make
gfortran usable.

Last but not least, there are even two ICE's (mayalias) in the test results
that I did not feel making an issue of.

Result, do not force me to contact these people directly when you do not take
the pain of even reading submissions.


-- 

michelin60 at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dje at watson dot ibm dot
                   |                            |com, mark at codesourcery
                   |                            |dot com


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


  parent reply	other threads:[~2007-08-31  1:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 18:10 [Bug fortran/33252] New: " michelin60 at gmail dot com
2007-08-30 18:23 ` [Bug fortran/33252] " michelin60 at gmail dot com
2007-08-30 18:35   ` Andrew Pinski
2007-08-30 18:24 ` dberlin at dberlin dot org
2007-08-30 18:35 ` pinskia at gmail dot com
2007-08-31  0:47 ` michelin60 at gmail dot com
2007-08-31  1:15 ` pinskia at gcc dot gnu dot org
2007-08-31  1:44 ` michelin60 at gmail dot com [this message]
2007-08-31  1:51   ` Andrew Pinski
2007-08-31  1:51 ` pinskia at gcc dot gnu dot org
2007-08-31  2:39 ` jvdelisle at gcc dot gnu dot org
2007-08-31  2:43 ` kargl at gcc dot gnu dot org
2007-08-31  4:33 ` michelin60 at gmail dot com
2007-08-31  7:59   ` Andrew Pinski
2007-08-31  5:29 ` kargl at gcc dot gnu dot org
2007-08-31  8:00 ` pinskia at gcc dot gnu dot org
2007-08-31 11:10 ` fxcoudert at gcc dot gnu dot org
2007-08-31 14:52 ` michelin60 at gmail dot com
2007-08-31 15:52 ` michelin60 at gmail dot com
2007-09-03 10:44 ` fxcoudert 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=20070831014351.26014.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).