[Bug fortran/33252] GCC-4.3.0 Bootstrap testsuite error increase

["pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #12 from pinskia at gcc dot gnu dot org  2007-08-31 07:59 -------
Subject: Re:  GCC-4.3.0 Bootstrap testsuite error increase

On 31 Aug 2007 04:33:12 -0000, michelin60 at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:

> Regarding the last quote I am led to believe that Mr. Pinski is taking undue
> credit. PR30758 (marked as a duplicate) is the first addressing the
> re-appearance of mayalias. there are another 5 PR, all appearing before Mr.
> Pinski's filing.

Wait one minute, did you read PR 28834 (note how the number is lower)?
 Also read comment #1:
>Note this is the testcase for
> 28807 which I was using for testing so the testcase might be added to the
> testsuite by the time someone gets around to looking into the bug.

Also you know what the testcase for PR 28807 is named?
(gcc.c-torture/execute/mayalias-2.c).  The other testcase was added by
me for PR 28812.  Notice a pattern here?

So how can my PR not be for the the mayalias testcase failure when I
filed the bug specifically so I did not get blamed for a testcase
failure :).  There is no re-appearance of the mayalias failure; just
for 4.2, the testcase was marked as xfail.  Nothing changed inbetween
I filed the bug report and the other one was filed except for the
tetcase being xfailed on the 4.2 branch.  I think you need to go read
more of the history behind this one.  Since I know all about this
testcase failure as I added the testcases :).  If you don't want to
give me credit that is not my fault but oh well.

I am getting tried of being wrongly accused for stuff I do correctly
by unknowns.

And again this is the trunk we are talking about so how can Mark be
involved for every day breakage?  Also if you are using the trunk you
have to understand there will be breakage and take it and report it
without being all offensive about problems like this.

-- Pinski


-- 


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